Open Telemetry Uncategorized, 30 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2022-11-30 meeting

Description

Open Telemetry Meeting 1's Personal Meeting Room

A

B

C

Hey hi good evening mark what do you think I said.

B

C

I'm, sorry, for being late, this.

C

Is let me share the screen, what we can discuss.

C

Okay, I haven't gone through, the specs updates, I mean still still not uh probably back fully with from the long weekend which we had so I just started. Looking into a few of the specs discussions and the PRS which have been raised uh but yeah, probably I, think I'll, let me go through once again.

C

um If any any of these are going to affect us, but but just just feel free to add anything if you feel anything in the spec exchange which we have to discuss immediately.

D

C

But yeah apart from that, um should we directly go with the issues and the pr, so we can probably discuss with some of the Mysteries which have been added to start with, and then we can go to the issues and appearance that will make sense.

C

C

Follow-Up after the latest breaks yeah. First thanks thanks for support, Mark and I think it's hard I think for fixing up all the issues which we had with the recent changes in the GitHub CI virtual machines.

A

Yeah thanks everyone. Basically everything broke here last week. So let's try to put that in.

D

The in working order.

A

C

Yeah and they're doing still are I mean you know fully that what exactly was the issue, because I'm still not very much Clear. Why a new latest version of GCC should.

D

C

Everything only change right, I.

A

Did not look exactly but I think uh it tries a new warning uh on some deprecated construct by default so that, even if you don't ask for a warning, uh you get one and that cause trouble. So and on top of that, it's it's a warning not only on code that we own, but it's uh there was.

D

Something with geography or.

A

Absolutely don't remember, maybe both.

C

Okay, so probably probably I mean to make it fully work, I mean if we still want to move to GCC 11. It should be something like we have to see if the latest version of those dependencies are have.

B

Fixed those warnings or not um I have raised the pr already for cmake I I think it makes sense to move everything to in into our own docker.

B

D

B

This issue anymore in the future.

C

I mean what but I mean moving to Docker is this is, which is probably I, think one way of doing it and I think that's something which probably we can move I mean I'm just concerned whether that will hide any of these issues which we are going to face with.

C

Providing us the latest environment, all the time and I know this would be a I mean we may have to fix all these issues and whenever they change the virtual machine, but at least this won't hide any of the issues right which we get yeah.

B

Sorry we just taking the control here with, with our own Docker I mean we.

A

B

Don't predict CI all of a sudden before release or something.

A

So the fact that Ubuntu latest changes that comes in a time that we don't control so yes, it creates some chaos. So if we move to a Docker, we will have full control and then we will not be surprised. However, uh when some someone uh some developer, takes open, Telemetry and try it on his own back into our Windows box or Ubuntu box. uh It should work so we should not. If we, if we do everything in Docker, we take the risk of it. We don't even detect, but something is broken on a given platform.

A

D

A

Will have a surprise when someone uh find a big report if they find one.

D

B

We we could, uh we could control that I mean we know when Ubuntu releases a new version and we just change our Docker and see what happens. We.

C

Can we can add a new document properties you can test and do we know I mean I haven't seen that, but is there any any uh difference? In the uh I mean the total total duration of the test or something I mean with the talker, because it's adding a new virtualization inside another visualization problem does it adds to any uh latency in the number of in the test time or something.

B

uh I should I think it shouldn't be that much.

D

B

And I and I have the version for bazel. Also working now I'll raise another PR for bazel.

C

A

So one thing I would like to to propose: we can definitely have new Docker builds, uh especially for things like if we take the GCC for it period, for example, uh that build uh we installed so many things on top of a base platform, but it does not even look like the base platform, so that one makes sense to be in docker uh if we, if we could do that and still keep one one Linux one Mac OS and one windows at least we won't be surprised by by changes also and another thing.

A

So last week a winter broke, but I'm suspecting that we don't have that off and I mean it's not that often but GitHub a great a given platform. So as inconvenient as it was, uh it should not be too disruptive.

C

Yeah I mean it's not the first time and we've been. We saw such breaking our NCI environments feed that till from pass two years or something so.

B

I don't know I, just don't like having broken CI.

D

B

The week before, like release, maybe.

D

It's not critical.

B

But I I don't feel good about it. Yeah! That's it from my side.

C

Okay: okay, let's probably let's go through that one, the window I just I'm just just concerned about, if there's any any latency which is which is being caused with that. If it is not, there probably I, think if you would raise up this one right.

B

Yeah, this is for scenic.

C

C

What was that? I hope? That was not because we don't have Docker anything right, no,.

D

C

When both of Basil do we know it will affect the caching.

B

Basal, uh it will affect the caching, it probably um I think it could be better with with my changes um but I I haven't touched the cash yet.

C

Probability to use the cash or.

B

Yeah sure it will um so I will um zip the file compress the everything that that comes from bazel, and we can. We will cache that one that tar file.

A

um By the way, so far, the bazer build was extremely slow for Windows and I.

D

A

On Windows, it is not using the cash, so what might explain it.

C

A

C

Probably we use I, think music package or something and then still for the installation of lots of libraries and windows. So yeah.

D

B

The issue for Windows is VC package, mainly for Jagger. Maybe we can remove the Jagger already.

C

Yeah I guess it's still not removed, probably, but maybe it would be windy. Eventually, it would be removed from the specification I'm saying it should be removed immensely.

C

I mean and I mean I I, don't have any strong opinion in either of keeping either of them. This was just the person I first I mean the first time we have been. We have seen that kind of this breaking of the world environment. Should we move it so or should we wait for some more time to see if it's not happening too frequent, and then probably we should move I, don't want any other issues coming with moving to a Docker, and then we have to fix up some other topics.

C

Probably we haven't yet realized that there could be some issues coming with moving the doctor, I mean so.

A

C

A

So this change with GitHub exposed a lot of breaks, but most of them uh we could have found them earlier if we were using more up-to-date dependencies. um So yeah.

C

A

If we make a better effort to keep up to date,.

D

A

Detect changes at our own pace as opposed to the platform forcing it so.

C

Yeah I think that that's probably I think we are not good at to keep at least all the different message to the latest I think we probably when something break, then we realize it and um yeah I think if we have more productive and totally again, then probably I think we may not have in this kind of issues and even if we get this issue, probably that will definitely surface out a real problem and good to have something break.

C

If it's a real issue, um I mean I'm, totally totally uh up for moving to Docker and that looks more safe and controlled environment I'm. Just that, probably we should to not do it as of no I mean that's my personal opinion and again not do it as of now, just just with one CI environment breaking for the first time. As of now. Probably, let's see if we can move things, keep things latest and if it's again happening, then probably you can do a more controlled environment uh in the docker.

C

So that's my opinion. I.

D

Mean I don't see.

C

Anything wrong otherwise in the topper I think that's pretty right way of doing it um to have a more controlled environment, but if it's I mean if something something else breaks because of moving to Docker or something else goes wrong, I mean I, don't know the speculation. Anticipation is something goes wrong. Then, probably this this current setup is working for past couple of years or something I mean we haven't seen anything breaking as of till now.

C

I I, think without virtual environment should be good enough. If we keep everything up to date in our own setup.

C

I mean that's, that's why I take but probably I think I'll.

C

Agree with what all you you mark pass on and talk what you always agree with. You know it's just my opinion on this.

C

Let's keep it I mean I think this is definitely a right path and right move to do it. Let's keep this.

C

uh Docker containers and probably have this PR for some time. Let's see if things are with the current setup, with moving to the latest versions, if we can still keep the things up to date, then we don't need to probably use Docker at all.

A

So we'll we will probably need to use Docker for things which are extremely different from the.

C

Platform like it's.

D

A

D

A

By the way, do you know why we support that um who is using it.

C

Why do we need photos? Yes, I mean 4.8 was the first GCC I mean 4.8 was the first I think, probably uh Ubuntu environment, which was providing GCC relevant support of four or three days of us. Sorry, GCC uh version with the GCC 11 support, so I. Think probably we just wanted to ensure that it works on that. Okay,.

C

But I I, don't I mean.

C

That support was not fully it didn't support it fully. So definitely that that person shows by we have special case for phone on it. We can even remove it. I, don't I, don't think any I mean that's a compiler which is not supporting C plus 11 to prevent all all the features of C plus 11. So I won't say it's fully compliant C plus 11 compiler.

C

Probably we can even remove that means. Ccc 4.8 support, I, don't see really, we want to really be compliant with that.

A

Maybe a mistaken but a recall from a.

D

A

Discussion but maybe Owens was using it environment, so if so,.

D

A

Should keep it okay.

D

Yeah yeah everything is.

C

Yeah, okay, okay, let's keep it I mean, uh but do you see we should move back to Docker I mean I, just just thinking why you should be we you're saying, because if we are not using a default uh Ubuntu package for that, we are probably installing photo explicitly and then we are testing is.

A

That the issue we are installing so many things on top of a platform, but the platforms.

C

But even if we do Docker, we have to still do that right. We have to I mean we have to take a base, Docker image, and we have to install all those things again same thing. We are doing in a virtual machine right, a virtual environment.

A

uh Probably I don't know exactly.

B

A

B

Pcc images, maybe.

E

B

C

Oh you're saying.

D

C

A

Yeah, it's not only GCC, it's also the proper version of Absol, the pop-up version of grpc uh and so on.

D

And so yeah yeah.

C

I mean if you want to move photo Tech to Docker I mean that's, that's fine. At least I mean if, if we feel that we can probably have a better to set.

D

C

With that, this fine.

B

um One more thing: maybe we could ask for some registry access, so we could have this image pushed somewhere and that would make the appears much faster because we are spending some time just for building. For example, grpc for this uh otfci.

C

So with raised to humans, we need some storage which can be accessible through CI environment and we can probably use that storage to store the pre-built uh binaries right. Docker.

B

Image registry.

C

B

Something private not accessible.

C

This is, we do have some I think. Let me see as part of the CNC for I mean open Telemetry. We should have got somebody's Docker registry which we can use. Let me see, probably if it's part of I mean it's coming from Azure or it's from so, but I find remember, going through Reading it somewhere in in somewhere in open Telemetry Forum uh for having me talk a registry which typically, we can use it, um but yeah. Let me figure out if it's there.

B

That would be an awesome time.

A

B

Can just make things much faster, yeah.

A

Which would speed up a lot.

C

Yeah, that will that will speak about you, that that will be probably one more reason for us to move to Docker images, if that, if that can speed up the pre, you can store the um based Docker images and directly around it. You download and run it probably something like that.

D

C

To probably finalize on this uh we're seeing that at least at least we can, we can have it occur image for 4.8. As of now and let's.

C

Oversee like, as of now, let's try to see uh how the the GitHub.

D

Environment behaves.

C

B

uh It's not gonna break I'm, sure.

C

Yeah, it won't break I, know, I, know and probably let's not oversee it, it's not going to break but try to keep uh the.

D

Dependencies to the latest.

C

A

So we will probably need two two different Docker builds, then one formulators and one for follow. It.

D

B

C

B

One Docker with arguments: okay,.

D

C

D

C

Are not moving, then we are not I mean just correctly, then we are not moving to Docker for the uh for the default. Our default builds with the latest right.

C

Just correct me I think it's okay.

B

I can write the docker file that you could say it's for for DOT a and then it will install anything that is needed for for that a and, if you don't just specify for that, they will do the latest.

D

C

B

B

E

Yeah and for the 4.8.

D

E

Think I I saw that the future Google tests will not support C, plus plus even 11 I. Think that includes the. This is a 4.8 right and I think we previously before also like some in our library like appsio, which has a plan and measurer, and it is already done or it is in apply. It only support you just uh let's see, plus plus 14., so drop the support for C plus plus 11 I think. Maybe we can check with oven to see whether he has applying for um for upgrade or.

A

So it will not support C, plus plus 11 I think we will start requiring C plus plus 14., okay,.

E

And yeah require.

A

Pc Also may do the same. I think.

B

Yeah and prompt is also did.

A

This, yes, so basically everything we need so.

B

Only boosted and we don't use boost and.

D

Boost is needed.

B

C

Okay, so this is the.

D

C

One more reason for us to really see whether we should keep supporting CPS 11 or we can also move to C plus plus protein in later, and then.

E

We have to do that right.

D

E

Just need to need to know how, when to draw drop and that's about four C plus plus 11.

C

Yeah, but all these again, all these libraries, though we are not sure, are not going to use Ctrl space 11 at the interface layer. Probably they may be using it internally and they may not be I, mean still with um well I'm, just thinking still building with Q, plus plus 14 and probably use it with. uh It should be still usable right for the.

A

um In one of the build breaks I saw last last week, um I think there was a bill break on uh the GCC 408 build using some latest uh adult remember if it was utter or something else, and it was breaking in some type trades somewhere using Thai internally by some adders in some Library. And so even if, in our code we don't use fancy construct, the library itself might have a lot of um yeah.

C

It's difficult to be Aviation yeah, even if you don't change the interface until it can be so.

A

One thing so I got distracted by the Builder break, but one thing also I still need to finish is to split the weave. Stl support by uh already is of C, plus plus 11 14, 17 and 20., because having things like more fine-grained will help to to upgrade from C, plus plus 11 to C, plus plus 14, later I. Think.

C

But yeah I think probably I think if we.

C

Start I mean if, if we can also probably not start supporting I mean not continue supporting C plus 11 in after some other version, probably we can get rid of 4.8.

D

C

Discussing a bit again movement, what this plan is yeah, it should be important because I mean we don't. We see most of the libraries now moving to moving away from C, plus plus 11. That's.

C

That means it would be difficult for us to keep supporting this episode. I mean maintaining so many different combinations is.

C

For us it keeps supporting so.

A

Many questions, it's not so much of a combination, but if a library is not maintained and if there is a sales bug in it, then uh we will never see a fix for it. So.

C

Yeah exactly right.

C

Okay, yeah, let's probably I, think I did plan to go through all the all the correct packages, both from Ubuntu Debian Android, hacked, probably try to see which all still supports the default compiler on all of them is which all have still supporting C, plus plus.

C

um I mean I mean supporting the GCC version, which only supports implants. They don't have that then probably you can move to C, plus plus bottom or so.

B

Yeah, maybe we can start announcing it in this, like Channel.

C

B

For many reasons,.

C

Yeah yeah: let's: let's do that? Let's have your probably some more figures on how I mean which which all which all packages packages are supporting it, the latest ones, still seated, including.

D

C

And probably then I think, probably let's, let's do some kind of announcement.

C

We got Mark, you were saying something.

A

uh Yeah well, if we just proceed to announce that uh we plan to remove C plus plus 11 and see if there is some feedback and everyone screaming loudly, but um but yes doing. An announcement already is a good idea.

C

Yeah we can do one slack, I, don't know how many of the users are really on stack slack but probably, and.

D

C

From there and.

B

D

B

An issue and pin it so everybody can see it when when they come to GitHub.

D

E

D

E

Not sure whether everyone will follow or receive our issue, maybe in our next release we can emit a warning during the build time to see and paste our issue link and ask people to to raise uh or post on the issue. If he still has, sales should still has dependency on C, plus plus 11.

C

Let's create an issue to start with, probably immediately, we can do that and.

D

C

Let's see the traction coming on that, if lots of people start saying no, we don't want to sub. You know we still are using that in C, plus plus level environment, then probably we will discuss it again, whether it's the right move or not. If we don't see much of the traction, people are like not much comments are coming and it seems that people are okay with the move, probably in the next release, we can uh give a warning that we are going to move away.

E

From special level incoming releases okay, so that sounds good.

D

C

But next probably here should we go to the next point.

A

We agree: yeah, yeah, I think we we all agree. So the next item is uh very quickly I'm, starting to look at how to implement uh SSL support for the HTTP oltp exporter and.

D

A

That, uh basically I need to have some options which are only available in some more recent curl and we trace the question: uh do we do we force people to agree to Carl and probably not because that will break some more builds already and if not, how do we do that? So uh the O'neill thing, but uh the only option I can think of so far, is to keep every feature behind the feature flag like uh or Wednesday, for the asynchronous change, for example.

A

uh But then we have a risk that we have so many internal terms, so many different features with so many different flags that it will add something. Some complexity as well.

A

How to how to implement features when we we're forced to use a newer dependency.

A

So this is basically this is upon Define. That says whether the library Booker library has this version or not, but those new options are only available in recent libraries. So, yes,.

C

So these three are probably only available in the in the 7.71 and liters. Okay and okay.

C

But I think this is we don't need a feature flag right? We can. We can support it behind the version check connect me I mean we can do that. If so this this these I mean if I'm, seeing these.

C

Okay, so if we see this property, this is basically if we want to read the certificate directly from from a memory location not from the file path. Yes, and if it's from the file path, I think that is supported with the older versions right.

A

So I haven't checked with most likely yes, uh so this is only when you, when you provide the certificate as a string directly and.

C

The string which.

A

Is so we have environment variable for that we have say certificate and we have certificate string. Yes, so this is for the certificate string. Part.

C

So in that case, if if the user is giving the certificate as part of the string and the version which they are using is less than 7.71, then probably we'll just give a warning, and we will I will give a warning and then.

A

Yeah but the thing is it's security, so I don't want the.

C

A

Silently fall off and and forget security just because yeah.

C

But not forget the security, the handshake should fail and it should not go through. So the assistantship should fail in this case, because.

C

And if any of this this is there, then probably we should ensure that we are not so relaxing the handshake and it should feel by default. If the version, if they're specifying the string and the version is less than 7.71, then then either. We should not continue at all uh saying that I uh this.

A

Is so surely conversion number it's a compile time switch so.

D

A

A car library is old. We cannot even make the call to give to give yeah.

D

It could not give.

C

D

C

D

A

This is a typical typical example, so this is a new feature and if someone is using that on an old platform, for example, uh VCC 408, uh it won't uh the code, Library will not be available for that. So.

D

A

Me try the question whether we we still do pontified in record to a feature Flags only on, if only if a platform is is good enough.

A

C

So if we use a feature plan.

C

Okay, I'm not sure how the feature plug will help again in this space I'm, just just still thinking here. Well, even if we use a feature flag and enable that feature he was reading from The Blob, but the version is old. Still that won't be supported right.

A

So it won't be.

C

A

Another question becomes whether this thing is a warning uh and we continue or if we make it a failure. So let's say so.

C

We should make it uh sorry, yeah, sorry.

A

Yeah so someone someone asked for HTTP, it works, someone that asks for https on an old platform and current is not there. So maybe we should fail, saying sorry, not supported. You need at least curves once.

C

I mean I'm thinking like this way, like I mean just seeing. If practically it is possible. If, if somebody is giving uh the the the the certificates, both the CA and the client certificates uh in the in in string and the version is less than 7.71, we can at least ensure that the handshake will fail right, that that can be done. That I think I.

A

Don't know uh because.

C

We should be able to do that. Yeah well,.

A

We won't be able to pass a certificate, so maybe we could. We use the default certificate and continue differently. It will not necessarily for never fail.

C

Like if we do this certificate validation as strict in that case, will it continue still? It will not be able to verify the certificate because there is no certificate to be verified unless until it's a default, CA certificate, that's for only certificates, I've.

A

Noticed it because I think it will use a default certificate for me as well and try to verify that instead yeah.

C

But it will okay can. Can we even.

C

Let's, let's probably try to see more, if even through, through setting some option, if we can even disable that okay um try to make it fail. Okay,.

A

Well, this is still working progress, so.

D

A

Obviously get this more, but I just wanted to have a some opinion, whether or other things I've used feature Flags in general. I know that very sync changes use a future plugin.

B

A

Not aware of other things.

C

Yeah we have been, we have been using feature Flags, but not for the scenarios where, for the different versions of a given Library how to behave it make it behave differently. I mean we haven't, used a feature plan for that.

C

But if you see that feature black can help in supporting any of the scenarios for curl version, I think feel free to do that. How many people that will that will ease out well.

A

It will it will definitely help to still support a plane, HTTP connection on every platform, because if we suddenly require a recent version of curl, a lot of platforms will fail to build, but.

C

Okay, so so what kind of feature plug.

D

A

C

Ssl, or enable just like that,.

A

Https Maybe.

C

Yeah HTTP SSL and if it is enabled then only will require.

C

D

Now, if it is enabled.

C

And uh and the user is giving the certificate path, then then we don't need a latest version right.

A

So we will need a different version: I've not checked, which one uh but.

D

C

A

It will be, it will be there, because it's uh it's not a new feature in card I mean.

C

Okay, so we don't, we I.

D

C

As such, I think there is no I mean I mean if we feel that we probably this will help out us in controlling the Google version. We are using or probably controlling the way we support, https https, then I think it's the problem. You can do that with the visual plan. Okay,.

D

C

We do have GitHub issues because curl is not the right choice for all the platforms. uh This is not not really directly related to what you have been working on, but probably just um no I forgot. It could have gone down somewhere down in the.

D

C

But I think the the idea was that yeah remove call dependency from Windows and removed curl differences from Apple platform, because these, both these platforms have uh default. Library, which supports https like CF, techbook, API and wind 98 API, which by default, supports HTTP and https.

A

So we have different implementation of SSL.

C

A

Different platforms, man.

C

Yes, so, basically that that's how our current implementation, uh at least the way way we started I have to still see. If we still are. uh We use the factory pattern to support the HTTP connection, where we can inject any of the client libraries, uh so I think just like color. It should be possible to inject any of these libraries from both Apple and Windows okay, so so that that's how right now the implementation is kind of factory pattern which should be able to inject or any of these libraries yeah.

C

But this just wanted to be yeah.

A

So what what can be another way to mitigate the dependency, also at least on some platform but foreign.

C

Let's come your winter break will take some time off. I think that's totally right time to take I.

A

Guess so interesting, some heads up.

C

Yeah I'll be away uh at least I mean that that's the tentative right now probably I think is probably the third week of December from 17 till 25th or something I'll be away.

E

Probably we could cancel meeting that week or if you must.

D

Have asked the.

E

Communication Christmas.

C

Week, at least you definitely, you should should do it for last two weeks of December well,.

D

A

Yeah, if you, if your Medicare is canceled, just say about on slack, and uh we will notice.

C

A

Think, like this I, probably.

C

Should definitely do it, do it for last two weeks, I think we last I think last year. Also we were not. We didn't have any meeting in last week for the summer as well sure.

C

From next release, yeah I think probably it's would be good to have well do it. Okay, probably sooner yeah.

E

I think you mentioned yeah transfers like somebody can change in 1.7. So when we know 1.8, so maybe we need. We want to release at least a patch version, maybe sooner.

C

Right, yeah, yeah and sorry about that. I think that was something because of me. I didn't really adjust. I didn't realize that we have uh two different Scenic targets, I mean so so there are the cmic targets which are generated by default, and then we also have the different CM Target names, which goes to the click config file. Well, I think that that somehow break break the things. I'm, really sorry about that, but yeah, but.

E

C

E

Yeah one more thing is about this package package: um yeah I was trying to like make metrics in the how the new implementation that default he invested package for 1.7 the same synthesis and build issue I. Think in you know, 1.7 code base learn some folder in the in the oh The Matrix folder, which header header folder like something called aggregator. But the folder is important: there's no no file on the data folder, so they say package compliance so actually, without making Source fixed, we have to count release a with the.

D

E

1.7 so yeah I'm thinking about moving to either 1.8 or 1.8 0.1 directly. So.

C

Yeah yeah I think that's a good point. Let's move in that case to username 1.8.1 or something and then.

E

C

Will have the real Matrix support that.

E

One has all the old metrics removed removed all the.

C

Code to remove.

E

The rest so yeah it will not be an issue.

D

C

Yeah yeah there are some Coastal.

E

Scanning in this package build yeah.

C

Oh okay, so even that activity folder it will not accept yeah.

E

That's not an issue I'm pretty header folder, but the the with the factory sort of then some issue happening there.

D

E

Create a number before doesn't need to complaints.

D

A

Some someone just fired a PR uh fixing a bug that I caused actually in the make file for uh open Telemetry portal and also recently uh with otlp grpc utils file.

A

This was added into the common library for the grpc exporter and not into the TLP grpc export. Sorry, so it was added to the otlp common library and not to the hotel, pgrpc Library, so very I have notified the issue yet, but there's a build break today. If you try to compile only with the HTTP exporter and not without the grpc and the break is that the.

D

A

Jpc util file is trying to include the other file from grpc itself when it is not needed.

C

A

Minor but very few things, uh yeah.

C

A

We can definitely ship as part of the 1819 East Van. um If we do one.

D

A

Know in December.

C

Yeah I think that should affect so. We are so you're saying that we all if we want to only build otlp HTTP without grpc that is going to break yes and because it's intertwined to include them. It's.

C

D

Before the next.

C

C

Can you create I mean if you have the idea, I mean Mark can.

A

You please yes, I will I will create the issue with the details. I.

B

D

A

Internally, because I I'm I started to build on when it's uh at zero and I just found that so I will find the issue with the details.

C

Thanks yeah but yeah I think Tom to answer your question indefinitely: will, let's have the new release, probably I, think next week or something I think it should be good to have it a very plot? If, if we.

D

C

Good enough with the changes with Mark is mentioning. Probably we can do it over the weekend or maybe in the next week. Okay,.

E

Sounds great or.

A

E

A

Me to say, because I cannot do or release myself.

C

Yeah, let's do it probably I think as soon as possible? We can do it.

E

um The next week, right, yeah.

D

Okay, thank you.

E

Are you going to make this release I.

B

Can do it no problem.

E

Okay, yeah yeah I can try to fix the Visa package and once we have a new release.

C

Thanks just just please let me know if you want me to do it, because this was something which I broke it I don't want anybody else, I mean if you want to do it. It's totally.

D

Fine, but this was I was a culprit, so this just feel free. If you.

B

D

Thank you thank.

B

A

B

um I was thinking. Maybe we need some script for that. uh There should be some.

A

B

In the uh kubernetes Ingress packets uh repository I will check that.

E

B

Release the script yeah, it really is a script, so It prepares every everything that goes to release.

E

Yeah I think we have aware I. Imagine better that one mostly on updates, like header fact or I, think the most manual work is make sure the change log is correct and the natural that one can be can be automated yeah.

B

Then they have something for that: I I think oh Victor.

B

E

B

C

Today, yeah the existing script will not do end-to-end release completely automatic. We just do things in bits and pieces yeah.

D

C

Was to add this script somewhere in the GitHub actions and it to execute it directly from there to make a end-to-end release, but somehow I think it didn't work.

E

C

D

E

Just to kick off some GitHub action and make a new release, it won't be there at your.

C

Case that that was something which I when I was writing. Scripts are I mean the that was the motive behind that to probably move it call it through GitHub action, but somehow it didn't work. So you just continued using it.

D

A

We do just uh do 181 release to four small breaks. I will then wait on your removal for the experimental semantic conventions, because it should be removed later. Okay,.

C

C

Okay, let's quickly, probably uh in the interest of time, I think we'll just quickly go to the existing issues open daily protocol, yeah I think that's already. The pr is raised.

A

Yeah so, which is very.

C

Very fast yeah yeah, add span processor option to set up CPU Affinity on on work, cut right, yeah, I think that's. That is something not I mean I, probably I. Think I just commented it here. That will add I, don't more of a native code and then we have to add that code for all the platforms. So.

A

C

It's a nice way of doing it.

A

So I think the use case makes sense. uh However,.

E

A

Are many things someone may want to set for Father, Fred and I'm thinking of some federal core storage keys that I might be using myself, I'm thinking of um named networks? uh Things like that. So if we have a solution where the user has some sort of callback where we can execute any code, they like on thread.

D

A

The FED starts and then referee dominates. Then we can put the set Affinity or other things if needed, and that would be a more more General solution so that we don't have a dependency on this Affinity stuff.

D

C

Yeah, that's something probably we can doesn't work.

C

I was thinking the other thing probably I mean uh if we can start supporting uh users to come up with their own thread. Library I mean they may be using some uh some some other site, Library internally or some thread Factory, which uses which is creating their own threads. Probably if you can allow them to add that, as as the uh as the optional parameter and then let let them figure out how how they are creating those threads, they just passes the thread and we'll use that 20 to create.

C

uh We will you just use those threats, we'll run our code in that thread. So something like this. If we can do it well, this.

D

Was specifically about this.

C

Case so we we want, we won't be bothered what kind of threat Library they are using. What's Affinity, whether it's speech rate or anything else, they just give us a handle for that, we'll use that handle to run our code and let them let them worry about what kind of threat option they want to use it in that.

C

That will also help us to support the scenarios where customers may be using their own threat, Factory internally for their own application, and they don't want a library like open Telemetry, to expire, new threats from within ourselves. Let them control how which or how to span the threads. Some people, probably more generalized here, yeah.

A

So people might have a fight pool also things like that. Yeah.

C

Exactly yeah, so if they have some kind of thread pool and they can pass, we can provide some custom interface, how they can pass it and then, let's probably, they can use that custom interface to pass us the handle for that and we'll use that to create a thread from the thread, pool and use that to run our um power code base game. So that's that's something I think probably more genetic solution, at least for this case.

C

Instead of start supporting native handles for affinity and all other things.

C

But yeah, let's see probably well, that's that's a good use case, I think, probably to start supporting and I think even I. Remember. uh Tom has brought this concern earlier. Also for about the applications which have their own thread term. I. Think that's something.

E

C

Supporting supporting in a very nicer way, so probably I think that's a good use case. It depends start supporting that.

C

um Okay yeah: let's now, let's continue discussing it in this trade I'll.

D

C

More details, but my thoughts for uh in this probably I just wrote some three four liners, but let me add some more details in this.

C

B

C

B

Interested to implement it, I don't have a strong opinion on any method. So.

C

C

Yeah sure I think that's that's something probably let me add some more details which I thought which I had and probably let's discuss in this and I don't know this. This original poster was also interested to add a PR for this. You have a feel free, I think if you want to really eventually.

E

C

And eventually, let's decide what you want to do in this, then, probably as on you can take it.

D

E

Since we are running out of time and we're sharing our meeting with the following one.

C

Oh yeah I think, let's, let's probably uh in interest of time, I, think any.

D

C

We want to discuss what do you think immediately and just let me know I think.

C

This tailback support I think they are wrong whenever you have time and yeah just started waiting on CLA this I'll I'll be reviewing, it I think I have some concerns here. Probably let me add my thoughts here on this: okay, okay,.

A

I will wait for the semantic conventions.

C

B

Thanks everyone bye.