Hi, Trista
Thanks for your reply,
As Host , We need prepare for some questions, especially when it comes to
specific technical details, community building and architecture.
About time， I think when we invited guest speakers , then make a decision
after discuss. Any day in April.
On Tue, Mar
I’d like to join the podcast if there is still a seat
kezhenxu94
> 在 2020年3月31日，12:06，Juan Pan 写道：
>
> Hi
> I gave a quick look on [1], however i did not find the exact time and
> preparation todo list for us.
> If I missed something, please correct me.
> Thanks.
>
>
> [1]
>
Hi
I gave a quick look on [1], however i did not find the exact time and
preparation todo list for us.
If I missed something, please correct me.
Thanks.
[1]
https://docs.google.com/document/d/1vT07pdk9AnDKilCOTaKkQfQEAMR-4gkatOOd8OFsjNY/edit#heading=h.vc1v9p9ru4sq
Juan Pan (Trista)
Hi Dev Team
After the experiences of removing endpoint_inventory, I found out this
strategy is successful.
Especially, we totally get rid of register, so I want to do more.
*SkyWalking 8.0.0*
First, it is already unexpected for me, we have to move to 8.0.0 so
quickly, but after the discussion
Hi:
SkyWalking member, committer , PMC ,
As you know , ALC Beijing [1] is ready, we want to do lots of things ,
podcast is one of them , others like write/promote articles, organize
local/online event etc.
As (ALC Beijing Podcast ) first show，we hope invite SkyWalking project
as Podcast
I will join this as the project VP, and PMC member.
Sheng Wu 吴晟
Twitter, wusheng1108
适兕 于2020年3月31日周二 上午11:07写道：
> Hi:
> SkyWalking member, committer , PMC ,
>
> As you know , ALC Beijing [1] is ready, we want to do lots of things ,
> podcast is one of them , others like write/promote
Hi SkyWalking Community,
Apache SkyWalking Team is glad to announce the Apache
SkyWalking Chart 2.0.0 for SkyWalking 7.0.0 is released.
SkyWalking: APM (application performance monitor) tool for distributed
systems,
especially designed for microservices, cloud native and container-based
(Docker,
kezhenxu94@163 于2020年3月30日周一 下午11:59写道：
>
>
> > On Mar 30, 2020, at 21:58, Sheng Wu wrote:
> >
> > Sheng Wu 于2020年3月30日 周一下午9:55写道：
> >
> >>
> >>
> >> kezhenxu94@apache 于2020年3月30日 周一下午9:11写道：
> >>
> >>> In essence, code coverage is a measurement of the code lines that
> **have
> >>> been
> On Mar 30, 2020, at 21:58, Sheng Wu wrote:
>
> Sheng Wu 于2020年3月30日 周一下午9:55写道：
>
>>
>>
>> kezhenxu94@apache 于2020年3月30日 周一下午9:11写道：
>>
>>> In essence, code coverage is a measurement of the code lines that **have
>>> been executed** during the tests, and the code lines that are executed
3 days+ passed, we've got 3 +1 bindings
Sheng Wu
Zhenxu Ke
Hongwei Zhai
and 1 +1 non-binding from:
Ming Wen
Thanks for voting, I'll continue the process.
Ming Wen 于2020年3月30日周一 上午10:42写道：
> +1 (non-binding)
>
> 1. LICENSE and NOTICE exist and fine
> 2. ASC and sha512 exist and are correct
>
Sheng Wu 于2020年3月30日 周一下午9:55写道：
>
>
> kezhenxu94@apache 于2020年3月30日 周一下午9:11写道：
>
>> In essence, code coverage is a measurement of the code lines that **have
>> been executed** during the tests, and the code lines that are executed in
>> the tests are **covered** actually, no matter whether they
kezhenxu94@apache 于2020年3月30日 周一下午9:11写道：
> In essence, code coverage is a measurement of the code lines that **have
> been executed** during the tests, and the code lines that are executed in
> the tests are **covered** actually, no matter whether they are counted in
> the coverage rate (~26%),
In essence, code coverage is a measurement of the code lines that **have been
executed** during the tests, and the code lines that are executed in the tests
are **covered** actually, no matter whether they are counted in the coverage
rate (~26%), my idea is to let the coverage tool (Cobertura
Hi Viswa
Add you to the receiver list. I recommend you to subscribe the mail list,
in case you missed the reply.
Mail to dev-subscr...@skywalking.apache.org
Sheng Wu 于2020年3月30日 周一下午8:56写道：
> Inline.
>
> Viswa Ramamoorthy 于2020年3月30日 周一下午8:52写道：
>
>> Yes. I gave have seen it. But in a release
Inline.
Viswa Ramamoorthy 于2020年3月30日 周一下午8:52写道：
> Yes. I gave have seen it. But in a release plugin keys would stay the same.
> Right?
The only case I know, which has the name changed, is due to adopting new
version of libraries. So, They change the existing plugin name, such as
adding the
Yes. I gave have seen it. But in a release plugin keys would stay the same.
Right?
Ideally plugins could be given a ID that can be a separate enhancement in a
new release.
On Mon, Mar 30, 2020, 6:25 AM kezhenxu94 wrote:
>
>
> > 在 2020年3月27日，20:25，Sheng Wu 写道：
> >
> > Hi Dev team
> >
> >
Typically a configuration like this could be both ways as this is a long
list of auto configured plugins.
On Mon, Mar 30, 2020, 5:38 AM Sheng Wu wrote:
> Seems acceptable to me. Just curious are real both ways required?
> Normally, people use an image tag to represent the agent(with necessary
>
Juan Pan 于2020年3月30日 周一下午6:59写道：
> Hi,
> I understand your concern. From my experience as PPMC of Apache
> ShardingSphere, both UT and e2e are necessary.
>
>
> UT focuses on a specific module, i.e., the part of the whole project,
> especially like SW core module,
> which is the most important and
Hi,
I understand your concern. From my experience as PPMC of Apache ShardingSphere,
both UT and e2e are necessary.
UT focuses on a specific module, i.e., the part of the whole project,
especially like SW core module,
which is the most important and less changed. Those UTs guarantee each
> 在 2020年3月27日，20:25，Sheng Wu 写道：
>
> Hi Dev team
>
> There is a discussion happening on GitHub issue. I hope that could continue
> on the mail list.
>
> Vr Vlaa wants to add a mechanism to disable plugin without physical
> deletion. I propose to keep using agent.config file and the names
Seems acceptable to me. Just curious are real both ways required?
Normally, people use an image tag to represent the agent(with necessary
plugins) for their different services normally.
Sheng Wu 吴晟
Twitter, wusheng1108
Viswa Ramamoorthy 于2020年3月30日周一 下午5:35写道：
> yes
>
> On Sun, Mar 29, 2020
21 matches
Mail list logo
