Open Telemetry Uncategorized, 5 Dec 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2022-12-05 meeting

Description

cncf-opentelemetry meeting-2's Personal Meeting Room

A

A

B

Good, how are you.

C

B

Hi Mark hi, hi Mark.

B

It got quite cold here.

C

Boom just come again.

B

It just got caught quite cold here.

C

I think same same here in Seattle also I think it's probably getting and getting very cold I think it's snowing nowadays. Yeah.

D

Highlighted hi.

B

D

C

C

Yeah, okay, yeah, probably I, think we can start um I'm going to see Tom there where I think probably he can join when we are in discussion. So I mean I, have couple of couple of I mean uh issue and a PR which I wanted to talk about uh so yeah. First of all, I think. Probably we can talk about the release. 1.8.1, your taxes, I, think. Probably it was done in a very quick time, so sure and I was just probably thinking just probably just a suggestion.

C

Should we have some tags to say like if we want to say I, don't know how we can do it, then this release 1.8.0, should not be something which people should pick. They can pick something older or I mean one version before that or one version after that.

C

But this is something which probably can break something if they will pick this and they will upgrade to the next version, so probably I think either some tag or something probably we can start adding I, don't know how we can do it if we can create a GitHub tag as broad or something so I. Don't know whether that will work but I think there is some something if we can add somewhere to say that this is something which can be picked up for the production or some of the.

B

Either we delete that.

C

Release that's one of the option or we mark it as something not should be taken for the production.

E

But delete it, you mean delete the data tag or.

C

Something else maybe I'm, saying really I, don't know whether we can delete the release from here. That's one of the options. If we can do it.

B

C

I've never seen.

B

Anything like that.

C

Or set it as a pre-release, which means that it's not it's not for production or some, some, probably if that helps or something um or I, don't know what will happen if you really delete the tag, what will happen to this release? I, don't I haven't tried ever let's see, um but.

B

Probably I think there's some one Link Break, probably.

C

Yeah I mean if and because will it be a link break because archive archive would so this will be still downloadable right, yeah.

C

D

So, do you mean how to withdraw a release then.

C

Yeah I mean somehow Market I did withdraw it or if we can delete it or if Mark, as something which should not be picked, not production, ready or anything, which says that this is not the release that you should use it, because, right now we are in this situation, where 1.8.0 is not something which should be taken, somebody who is on 1.7.0 they should directly go to 1.8.1. They should not be picking this release. That was our mistake that we put some something which unknowingly broke uh Prometheus exporter, um so.

D

um I would not think too much about it, because adult really is is by definition, some fix on top of something Zero release. So people should expect that and also yes, some parts were broken, but if someone is not using a specific exporter, it's working fine for them. So what we can do is add, maybe add a commenting for original website saying. Oh, uh please, take 1.8.1 instead, for example, but I would not mess with the taxes in git and create more chaos.

C

D

B

D

And if you look at that, I mean every release done from from the early ages until until now should be reformed, then so yeah.

C

Yeah, probably we never discussed that I think yeah, but yeah justification.

C

E

But um I think you know I think we can. We can't like um we struggle are deleted that are released, but perhaps it is good to not push them to to the package managers right I think that will be good.

C

Yes, I think this. This was okay, I mean 1.8.0, because this was just breaking, but I mean if we come to some situation where we are normally annoyingly do a release and that was breaking like complete SDK or something uh probably we have the thought. We have to think then. What to do to.

D

C

D

But also in case of beat tags, uh people might have their own branch on top of a tag, so we should never touch that yeah.

C

Yeah so I mean we should not I mean not to remove any existing get tag, but probably uh yeah I mean I, don't know if there are some tags here which we can put here. I mean not the GitHub tag, but some other tag which you.

B

Know not the git.

C

Tag but some other attack, which you can put I mean I, don't know, I, don't see anything. Let's.

E

See to the title and to say it is deprecated right.

C

Yeah, probably probably that's that's what we can do something put something here: yeah.

D

Yeah, you can see we've drawn.

C

D

Things so far, but yeah.

C

I think it's okay! As of normal. It's not! It was not breaking something substantial. We don't need to withdraw this release, but I think going ahead. If something happens, probably we have to think I mean to mark on those trainings.

C

Okay, yeah, that's fine, I mean it's.

C

Apart from that, I think I probably just wanted to talk about uh unless there is something really urgent which we want to I mean something more important, I think I just wanted to discuss about. uh So there was an issue which was raised long back, um allow to build a SDK and content reports via the build contract option build option, so I mean that this was something I mean I. Think Max has put has suggested this approach, uh basically for um the.

C

uh If you want to build any external component, which is part of contract Depot or some sort of somebody has created a non-standard exporter uh and they want to distribute that exporter to external users and now consuming that exporter is a very tedious task, so it has a dependency on open, Telemetry CPP. So, first of all, anybody who want to use that exporter has to First install open, Telemetry C plus place. We don't provide any binary packages to go through pardon.

B

C

Okay, so we don't provide any binary packages, so they have to go through all the steps and meet the dependent meet the dependency for open television, C plus once they have done that, then they have to go to that non-standard exporter, which is there in some external repo, and then they have to start building that and then they have to install and then they have to. Finally, they have to because that's that's how they have to consume it.

C

So this suggestion was like if you can provide and as part of cmake, if we can provide this build contract uh cmake option where people can provide the external repo which drinks and nons, which brings some exporter or any other component which should be built along with open Telemetry and this what's what our cmake list will do is that when it sees this build contract, it will basically add this app directory and uh path to that repo- probably probably clone the trip over in as a sub module or something, and then just do ask for directory to that.

C

Rep, oh and then build the entire tree of open Telemetry, and that will in turn will also build the uh the com, the exporter, uh the outside exporter, along with, along with the open Telemetry and then once we support RPM that one you get packages we'll have a single RPM which contains everything, open, Telemetry or also the external component.

D

So so we shouldn't it be that done the other way, because it's the.

C

A

D

That has bitter dependency on open telemetry, so the contrib can do its own repository and do an AB subdirectory on open, Telemetry, CPP.

C

D

And do all the packaging them.

C

Yeah I think that was somehow it was discussed and.

C

Yeah I mean yeah, probably I, think that should be the right approach. I think I, agree, I, think that's probably. Instead of that, we should I mean those external exporters, should Maybe provide open Telemetry as a sub module and yeah I.

C

Think, probably that's what that's that's, how the discussion started and I think that that was one of the reason why we didn't agree on this approach and probably we um stopped it, but but yeah they probably go through this I mean I just wanted to talk about that because I know I know some people were facing issues with building external component with open Telemetry and then I realized that we had some discussion doing this way.

C

I reopened this issue just to talk about that, but but I think that's I didn't realize that the other way of doing it that once I was opening it but yeah that that's I think that's something which should be the proper approach of doing it other way and okay yeah thanks I, think probably I'll.

B

I'll just I'll go through.

C

This once again and I think it does not make sense. I'll close this.

B

And I I think having some examples would be helpful, like end-to-end example for build, especially because it's it's tedious and you have to um yeah.

C

B

Many things about our repo.

C

B

If you don't know what to do, oh.

D

Yeah, in any case yeah it is tedious and uh it's make file hell. So an example would be good if the the thing my.

C

D

The dependency come from elsewhere, so something we don't control, so I don't see if we have certainly a dependency on something which is unknown. How can we, uh how can we do a build or not? Can we do our knees or can we enforce that.

A

D

Don't break the binary compatibility things like that if we have a random dependency yeah.

C

Exactly I think that was even I mentioned that open Telemetry has not dependency on any other repo, so we should not be adding that yeah, but I think I, just probably even um we should choose, people were I. Think probably we are missing the examples and that will I think help and I think one of the examples.

C

This approach, I think I'm already using it somewhere, uh probably in UND or um which.

D

In any case, isn't that what the country boy is supposed to be for.

C

uh Yeah yeah that that's that's what it is for, but I think building some something which, in the contribution, how to build that was something probably was more of a discussion.

C

Yeah, but contract paper will contain all the nodes, all the components which are non-standard, but how to how to build them. If we can provide some some plug-in in the main repo to build the components in non non oven in the content Depot, so that was something which probably the discussion was about, um but yeah I think it should be. You know it should be the other way, I think, as you said, I don't know whether it be any of them are doing it.

C

You don't have that, but probably yeah, probably I I'll, try to put some example on using the other approach which Mark you are talking about. If we can include open Telemetry as a submodel in one of the exporters and try to build that, and probably give that example documented examples.

C

Okay, I think, probably that was what it was all about, and some activity or in memory exporter, yeah I, did see.

B

C

Was just words.

B

D

So this one from Jan in uh in July and I.

A

D

Just a bunch of commits are, there was one thing he did is he did a force push, and this just totally erased the history of what what happened happened before.

C

Okay- and this thing is, he has done on the approach of not using Okay okay, so there's no adaption, probably just merging with the main or something right, of course Behavior. Okay, probably he may I mean I presume he may want to work on this or something that would be one of the results.

C

Thank you yeah, but I. Think probably we just need to wait and watch he's going to do any changes.

C

Yeah, it's still with me so probably I think I'll.

A

C

It's assigned to me because it's always reviewing it here. It's not Market stale.

C

B

Know hope that he's going to work.

C

C

C

And yeah and I, just probably this is something which I have been working on for some, not this kind of something. Oh, this is enabling CLA how come it came into so I gave it wrong.

C

Yeah. Probably it's a wrong one. 662.

C

Okay, not this. We are sorry I just wanted to talk about this. If only I'm going to interview this I mean I have tested it with both Deb and RTM, and it works. Fine I have to test I. Think most of the changes suggested I have done it. I have to test. Only one of the scenario which Sergio has been surgery has mentioned uh issue with the protocol.

C

Developer was saying some issue: I just want to test it. Otherwise, apart from that, I think all the concerns there is that fix that and also tested it with both RPM and depth, and it works fine along with the dependencies. You know it's probably marking the dependencies also properly so it'd be good to go or nuget is not yet there, but that's my first.

C

My I mean personal interest to support you get package specifically for Microsoft, I, think so probably I'll not as part of this but file and after this I'll start creating you know, one phone you get also support should be very straightforward, but it's more about a testing if it works, fine or not so feel free to just review this.

C

And I think that this this I tell that it's important because they have been multiple asks right recently coming for this, and also we don't, we don't provide the boundary packages, but if we can facilitate scripts to to develop the binary packages, I think that also is a good thing.

A

C

C

Yeah I think we do have an issue for that.

B

Yeah, it's paint yeah.

D

It's been and I'm I'm surprised. No one said anything I mean.

A

It's yeah totally quiet.

D

By the way, the story on Prometheus is that oh and actually fight the back on uh on permit use itself to ask to go back to C, plus plus 11.. So.

A

D

To go to C, plus 11 comes actually from from open Telemetry. Well,.

A

B

I didn't see that.

C

Oh, is it yeah.

C

Okay, this is okay, he.

D

Didn't do the fix, but.

C

D

You find the issue for that.

C

Oh okay, you didn't see that yeah.

D

C

I think probably that's the reason why oven is.

D

Not complaining what is his name right now, so.

C

Let's put this here: okay, probably I, think we should I mean if I understand, we have to wait for some more time.

E

On this issue, to be sure, he's aware of this.

C

I think you should have seen it so.

E

C

If you want, we can you I.

B

A

D

Yes, I expect you would have some something to say at least.

E

D

Depending on whether we drop it or not, I mean obviously it will not happen over uh in.

A

D

So how should we first of all, if we drop C plus seven? How long can we keeps reporting it to provide people for for enough time to migrate.

C

I think once we drop it, I mean please correct me. That was that something with with my understanding is once you drop it. That means we don't support it at all. Before dropping we'll give some grace period for people to really move out of stop using using that c57.

C

They should stop using it, but I think once they drop that when we drop it from the CI will modify our code to use, make unique and anything else.

D

True, so I mean how much time between the announcement, if we decide to drop it and and virtual uh lack of support.

B

That's my that was my idea. Six months. Okay,.

E

Yeah I think also depends on the ask right and like if the user we haven't got any users requests to hold um C plus plus 11. Maybe we can be faster. So, yes,.

C

D

Whether we are in development or in production, or not using it at all, also this kind of things.

C

Yeah, probably I think we'll keep. This will I mean I, think we can decide it by end of December. Let's see if somebody is really responding on this and then probably will take a call uh in early January for the time frame. Sure I mean, as Thomas said, that probably we don't see much of the traction much of the comments on this issue. We can definitely make it much earlier than six months.

C

Create the separate pipeline, uh what grpc and HTTP yeah.

E

I mean it's a separate, the Bose pipelines, I think um the also in real code. I think um it is rare that to use both grpc and HTTP at the same time in the same Library. So maybe we need to will be better like to more close to the user's code. If we separate them into two different pipeline testables.

C

This is this is for the uh for the reason like okay, this is not to increase to decrease the build time, but this is just to improve that.

E

Yeah, that increase of your time.

C

E

Really decrease a bit of time because.

C

E

Will build less red for each.

D

E

Separated the pipeline.

D

Yeah yeah well so, instead of having a build with both, you like a build with only grpc and another one, with only.

E

Http yeah, that's right: yeah, okay,.

C

E

Don't be buildable set at the same time, because that's what I think not the real case code right, okay scenario, yeah, okay,.

D

Although for some things like um the the warnings with the maintenance mode for valgrind from uh esan things like that t-san and those kind of builds which are almost pretty much doing, QA, uh those probably should keep the maximum of features so test. Both job PC and HTTP get the.

C

Same yeah, probably it won't be one CI test, but there would be multiple creators, but each of them right, yeah.

E

I think yeah yeah. You think that that's a good way to for testing, maybe I can I can proceed to on that.

E

C

That's that's fair tonight, Tom you'd like to create an issue for that and probably yeah.

E

C

E

C

C

Okay uh and probably you can discuss the rest of the GitHub PRS if we don't have anything, if you want one definitely I think probably do we have probably simply Market any holiday plans which we have.

C

That will give us a fair idea who would be there? I mean this is not something to control anything just to talk about when people would not be there, so we know that they want. They won't be any activity happening. So probably I can I can say that I won't be available from sound 18th December till.

C

24Th or 25th I think it should be I think but description.

C

And probably just just put your way, nothing just just an idea and you we all know that.

D

Okay, I don't have some from some firm dates yet, but expects some low activity anyway.

B

uh I'll have less activities next.

E

Week, yeah I will I think I will be taking vacation. Maybe in the last two weeks of December.

E

And that's winter break time from 19 to 30., so yeah.

C

Oh okay, Tom, then I think we need to talk about this. Let's talk about this period, I, don't know who is supposed to be there so this this week we both want to deal right.

E

C

D

Just to clarify: are we expected to attend some meetings with architectural or somebody else in that time, or is.

A

D

No, none of us are there for for sales. For two weeks.

C

Meeting which we have to attend, um but just to keep, have some idea, so I, don't I, don't think there is any blocker for which we have to be there for those two weeks or something uh but yeah. This I was talking with Tom regarding Microsoft internal because we both are handling some of the stuff. So so, if we both are not there on this week, I think somebody has to take care of that, so that I was talking with time. On top of those aspects.

E

Yeah we can think offline. Maybe my.

A

C

Unadjustable I.

E

Thought usual: you will be off in the next week, but not not in the case.

C

Probably I think that should be fine, I, think I I think they would be anyway less of the activity, so I think we should be able to manage it.

B

um Next week, only.

C

C

In general, which would be I think for all of us, I think, probably last two weeks or three weeks. Something would be anyway and less of the activity and.

C

Which is which is a big.

C

Yeah I think probably we can quickly go to the PRS.

C

Yes, I think you have raised this PR I mean no I didn't understand completely what we are actually trying to fix here, but probably if you can just.

B

C

B

You remember this image that I created for enabling them multi-platform builds.

C

B

This is the fix for that one, but.

C

B

There's one problem for that for multi-platform: it is not possible to save the image on on disk when it's built for different platforms.

A

B

Is only possible to push the image and you don't have that and but this PR, what it does. It's It prepares the build image, so we can um use GitHub, upload up, artifact and download artifacts, and this one reduces the time for build time for grpc OTL pgr PC to have.

C

B

Just brought it uh if everybody is okay with that, I will push the grpc one. uh It's in the description, how it should be done for the grpc.

C

Okay, especially for grpc, you are saying it so it's going to upload the okay.

C

Okay, we've received.

C

C

As an artifact, it's going to upload yeah.

B

Yeah, it's uploads to GitHub, and it it survives uh two weeks and the crown drop that builds it uh mechanical. How often I think once a week.

E

B

E

Public downloadable, or in just.

B

A foreign it is public.

C

But I mean uh I'm just thinking about a different approach here like if this is basically to reduce the time before I mean for for the build for OTL period, yeah I'm, just thinking can't we use the cash the way that the way we use it right now for.

B

Cash is already almost full. We are I, think we are consuming like seven and a half gigabytes already.

C

How much is the limit is.

B

10 gigabytes, the limit is 10 gigabyte.

C

C

Probably, in that case I think we should request for the um upgraded or Ci or something. Let me, let's probably see everything.

B

If we could request one something, I would request for a registry to push some image.

D

C

But why I mean sorry, sorry, but why to question registry? If the cash it would be implicitly cash the grpc building made, and then we can use it again right from multiplication. We need a registry. In that case, you know.

B

C

Mean you can build the grpc, probably we should not build it and install it in slash, opt or slash user, like probably we can install it in some home Runner or something and then cache the home Runner and then reuse it again. So the way we do it here, I mean visual cash, yeah.

B

C

So probably install it here somewhere in dot, cache grpc and then probably we use it from there.

B

Can't wait to do as well.

C

I just want to see, probably because, even if in the current setup, if we can do that, I think that probably would be a I'm.

B

Not sure how much.

C

Size grpc takes if it is within the 10 gig of limit. If that, if 10 gig is a limit, then within that limit, probably I think we'll try that also I.

A

Mean that's just something.

C

I explained into my mind.

B

C

B

Is like two and a half gigabytes, so I expect the same thing goes to cash.

C

E

And it's job is built by passing in the same maker right.

B

Yeah it's by C make and one more thing about the image is we can have multi-platforms, you cannot have it with cash.

D

So so that I understand this image with that contain only source code like the source code of upsell and.

E

D

And so forth, or is it binary compiled with a given compiler for a given.

B

Platform yeah, it's compiled. Sorry, it is compound, so you just uh everything is ready. You just compile open telemetry.

E

B

If you get registry, we can do multi-platform, that's very easy, then okay,.

D

But with cash we cannot. If we have such an image, is it possible to keep the the build Logs with the image so that we can be inspected if we need to investigate something.

B

Build the logs on on website.

D

And like if I, if we compile job PC and there's a warning for a given compiler, which is forgotten and the binary is in the cache and that binary is rotten and causes some failures, how would we investigate, but that binary was not built correctly? For example,.

B

No, no, we cannot see the grpc.

B

We could see the logs for the image, build that that's how it goes yeah yeah, but after that, when we consume it, we will not see.

B

The other benefit this one has is I I personally, don't like to have a prepared setup anywhere. I just like to run some comments, and this is just makes life much easier for me, whatever on the CI I'd like to test I, can do this with this one. It's just bash ci2ci, sorry, CI branches run Docker and then the CI part that I'd like to test.

C

D

Well, it's so that today we spend more time building job, PC again and and all the dependencies without compiling open, telemetries itself and testing. It will speed up a lot.

C

Yeah is something which probably we have to speed up. I. Think I was thinking about the cash because being basal it works. Fine I would bezel builds for grpc are very fast, uh but yeah that that's the bottom like if we have the limit for cash and.

B

I, don't know who who we should ask for okay,.

C

It should be cncf level, it won't be something.

A

C

To our so but yeah, probably, we have to call check with the GC Committee of open Telemetry if they can request cncf. For that that's the approach it should be and I think there was. There were some discussions on this um for asking for the upgraded virtual machines, more faster virtual machine with higher configuration I, don't know whether that was that request was raised by the demo team, uh open, Telemetry demo team to for the higher config virtual machines, and that request was I.

C

Don't know whether the open Telemetry GC has requested to cncf or not, but probably let me let me find out the status of that and if that's the way, if you want to get for the registry, I think we can request another history also, whether that's probably that's that's, let me see how they request it for the higher higher config virtual machines, we can use the same request format for the for the registry or something for the higher cash limit indicator.

C

Let me try to find out that.

A

B

See that issue.

C

And let me try to figure out in that discussion was somewhere in the community demo. I, don't know.

C

I think it will take time to do this for me to track that down. Let me find out that issue, and probably we can use that um who replaced thanks.

C

They requested for a higher conflict, virtual machines because of C plus plus and PHP the build for simplest way. Then PHP was taking lots of time. So that was the reason why they have asked for the conflict, machines and I think that's a more genuine request for us, also for C, plus plus in.

B

That case, if you could get a registry, then of course we could be fast and foreign.

C

That will not mean right that we have to convert everything in Docker, because that's something I don't want to do it immediately in current state I mean move all over CI pipeline to a docker.

C

That's something probably a I'm, not sure whether it's good to do it, um that that was the only concern I had with the registry. I mean I. I'll, probably prefer to that. We build everything on the virtual machine directly, not not create another virtual machine on top of the GitHub version machine and test it everything. On top of that.

A

B

It shouldn't be virtual machine Thursday.

C

Yeah, you know as a Docker, it's not a virtual machine, but still still it's it's a virtual environment. On top of another virtual environment, not a virtual machine I say it's not a hypervisor good virtualization video.

C

A

Yeah, let's, let's discuss on.

C

That I mean I'll, say probably, let's probably review this PR I mean if you feel that it's something which is good enough to go.

B

It doesn't change anything yeah.

C

But I mean that that's that's something I'm I'm I have concern that if it's not changing anything means it is not being used anywhere and but I mean do we have any scenario where it would be used. How can we use this.

B

I mean if, if everybody agrees, I can make the grpc build faster. That's the only used that we have right.

A

B

C

C

E

Let's probably.

C

Review this I think it's okay.

D

C

Haven't seen that completely okay.

D

My only request would be to have some minimal documentations so that we can throw I mean just to have a big picture of which part is where another.

E

D

Fit together, uh especially like when photos of beer boy just to understand, which part is doing what so that we can troubleshoot that.

B

Okay, yeah sure, thanks.

C

You integrate feedback. This was something more of a redundant PR IDE.

B

Blocked PR by requesting change, I think this is yeah I, don't know if everybody is okay with that, like.

C

Should it be good to close it actually uh I.

B

C

Him to close it himself, uh but I think he didn't close close up here, so probably I think once once that the other PR get merged I think we should be good to close this fear. It could be more attendant. In that case,.

C

Update clone command solid empties. This should be good to go right. I. Think someone missed out merging this year.

C

B

I should close it.

C

Implement, okay: this is something okay. This is something work in progress, yeah, so.

D

This is my new toy.

D

Basically, I gave up using the grpc exporter, so the only thing I need for the HTTP is to have SSL enforced, so I'm trying to close that Gap. But.

A

D

Working progress I still need to do a lot of investigation and not to mention testing So, speaking of which for testing I have no idea how to do unit test for testing SSL and how to do some integration tests and like.

A

D

With a real communication, but it actually works as expected: I don't know if you have any ideas on that.

C

Can you see this if we can I mean I haven't gone through this completely? But if you think that we can somehow enhances enhance this for a strategies and just use this for test, so we do have an HTTP server which we had been earlier using for our our com earlier. Our complete unit test was not mocking HTTP client, but it was basically using this HTTP server.

C

um We dropped using it because of some issues of time, timeout and all this stuff coming from this server because of that I think we removed we removed using and we stopped using the server, but just just see that it means we can use this server for SSL handshake to probably enhance it for testing assistant I, don't know if that's something which is doable and then have one a real test. Using this server.

C

I mean if this was something you were asking about, something probably different.

D

E

D

I'm asking in general how we can test SSL, but.

A

D

Not quite sure how to proceed, because the obviously that could be tested and yet at the uh on the offer and SSL is by itself very complicated. So it's so nicely to be tested using.

C

D

Consideration code.

C

Okay yeah, so that that's not something which I had in my mind. Probably you can, if, instead of mocking it, if you can use a real server, um if somehow, if this can support SSN I, don't know whether we can add open SSM or something with this and probably support it or uh you want to use some other external https.

C

So, for you read test I, don't know that can help um which I'm just thinking about how can we do it.

D

Because for real test, for example, for to test the trace exporter or.

A

D

Not only we need a server, what talks HTTP.

C

So it has to be.

E

D

Also, it has to understand where jlp protocols, so it just would be basically the open, terrible.

C

D

C

Oh okay um should be not just yourself but achievement only something which can recognize this. The drpc request so.

B

um Maybe you could try the hotel collector in some test, I'm already doing that for Benchmark. Okay,.

D

So yeah try to try everything here anyway, so that uh not only tests https, but it will be a full integration test.

C

Yeah I mean I, don't know how can we integrate that as part of integration test or something the real collected, but yeah, probably there's something you can try.

B

B

There's a collector into CI.

C

Yeah yeah, sorry, oh, we haven't enthusi yeah.

B

I use it for benchmark test.

B

Yeah, it's line 22.

A

B

You can change the config there.

D

Okay, so, presumably, if we put the SSL shot and whatnot in there.

D

D

D

Oh and a related question on https.

D

Wanted 12 or so TLS- and this is not part of a spec yet so we filed an issue and respect trying to uh to ask to add Tres on the on the specification itself, but it got no tractions, so I'm I'm only English should we do I mean. Should we wait until the specify arrives, or can we go ahead and start to do something? In the meantime, 40s.

C

I'm just trying to open that issue of the illness- it's not here. It should be.

C

It's been ntlers.

D

It's not exactly this one that is closed.

D

Yeah, probably that yes.

D

So we need to tears version and Cipher list which are not part of uh HTTP exporter options, and you are not there because there are no environment, viable introspect. For that.

C

But this was a difference so.

D

This is the request.

C

D

The spec, it just got no traction whatsoever, I mean no one even commented.

C

Okay, so now I got it so you're saying that specific minimum number of DLS.

B

Version right: no, we.

C

Should not do anything for this unless, until this is part of me so you're, adding some environment variable or adding some content I think we should not support it until then. It's part of the specification okay.

C

That's interesting to enforce HTTP 1.2, okay, 1.2 plus okay, so that means 2.0 and short sentences.

C

And just think why it needs configuration in the client. Okay, the server is supporting 2.0 or 1.2 dot. Plus client will automatically use will agree on the higher protocol higher version of protocol right. That's how the handshake works right, so the server will send all the yeah.

D

C

D

Point if you want to enforce a minimum version, is that you don't rely on what the server says. If you talk to a bad server that will accept any crap where you don't want to talk to him.

A

C

Yeah but probably I think this. Some some should get editing specification, yeah.

A

C

And I think Carl does not supports TLS 2.0 out of the box foreign.

C

Libraries to support 2.2.

D

So I've seen some API in kernel for sales version and ciphers, um but they seem to be different for uh TLS 1.3 and for other things. So I did not understood exactly how it works.

C

Yeah, but probably I think anyway. This is something you can wait till something gets in the specification I mean if we want. Probably we can comment on that to get more visibility on that issue. Okay,.

C

Spin lock for you, this is something which we are already waiting here. I think like this is I. Think probably some more. This got missed. Sorry.

C

A

Think I'll review.

C

It probably if it is something good we can let it go sorry if anything, it's been waiting for life.

C

Thank you and yeah big spin, lock, I think this is fine, but we are waiting for the CLA after sometime I think if it is not I'm, not sure, if he's not able to fix these fixes, CLA, probably one of us can take it forward.

C

D

Yeah, so we can also. This is for a brand new compiler, also I, guess for this very low demand for that. Yet so it's not urgent.

C

B

This is not free, compiler right.

D

I, don't know, maybe not it.

E

Should be free, but the network insurance I think.

C

This in the interest of time again, this this is I think this is something which looks good now after the recent changes we saw, Windows done I just want to go through once again for the rest of the stop just to see everything is fine. Okay, I think I'll review this and.

C

Get this I think we should be able to review it now. Right should be good.

D

uh Should be yes,.

C

I'm; okay, with that.

C

Okay, I think that's all probably already discussed about the rest of them just quickly. We can go through the issue. I think this three minutes, so nothing I need to do but time management on joining the meeting. I'm. Sorry about that we got multiple issues come.

B

From I'm promises.

C

C

Support, obviously, we will decide I'll take care of that integrates even with certain this issue. We discuss Matrix producer support, I. Think I can take care of this. It's.

A

Not something very urgent.

C

So it's something I think optional to support or everything is not various take it towards where we already discussed that add bath, pan processor option to set CPU activity, yeah I added some some example: how we can do that instead of adding the Affinity support inside the SDK, if let let the application bring the thread to library with the required logic and let them so. Why does something I think you can do it I think he said that he'll do some work on that only we can do it.

C

I think I, think this is also with you, but I think that if you may want to wait for him to really do something and then probably you can take it.

B

Can I'm very interested in that one.

C

At the Cici test for Mac OS here is nothing I had a comment on that.

C

We don't have any tests to realize that on Mac OS we just have a basic test. We don't have to make this to really test anything on that.

D

uh What we had or maybe yeah, maybe it was based on only yeah.

C

Yeah I think this is something which we have to fix it. Now, it's probably coming in this area. We are seeing lots of time. We are thinking things I, don't know why it is very impressed of all but I think anyway, so you have to fix my.

B

Oh, this is coming from the script I.

C

Yeah I mean I, don't know why it is going here in the error message. Rightly, the benchmark test should not fail. Yeah, probably we have to see.

C

Okay, we just have one minute quickly if you can see anything important in this.

C

uh Yeah, this is CI baseball, does not build on 2.204 I think we we should have another issue that CI builds, are not working on latest GCC, um C, plus plus 11 I. Think, okay,.

D

A

Of which, should we.

D

Try to upgrade our dependencies in general or moving to the latest component and whatnot I.

C

Was thinking to start.

D

That, with the warning uh bid on maintainer mode.

C

Yeah I think probably that's a good idea to definitely upgrade uh actually, at least in in the maintenance mode build at least we can try to upgrade every Everything, along with the latest of compiler, on Ubuntu 22. For probably, if you can try to see if that would be really nothing.

B

One question: do you know if everybody has the same Ubuntu version on on the CRA like when you do open to latest I think my Fork is if I raise a PR against my own Fork I I think I get the old Ubuntu, not.

D

The noise, so as far as I understand uh GitHub do uh rollout account by.

C

D

That so it takes something.

A

D

Or three months, so uh there is a time where some accounts are upgraded and some are not, but eventually once the Ubuntu migration is complete, everyone will be on the new latest.

D

So it's a it could be that there is a difference, but it's only a temporary. It's a transition.

B

D

In my understanding.

C

Yeah I think that that's right, it makes more of a face dot deployment.

C

So it made it from time now: yeah.

D

But you cannot do the noise when debugging things sure.

B

I just didn't expect that they are testing on a report that has so many so much more years than mine.

C

I think this is the other way. Probably they deploy it on something. Something right which is something done. The male repo build is something they will do it first, because that's more important and then slowly they will do based on, but actually.

A

It should be the other.

C

Way so that people should be able to test it in their own.

C

Oh God, okay, I think in test of time. Sorry I think, probably next time, I think I'll try to do a better management of this I think we are not able to go through most of the issues and that we are at least the issues from last two meetings. It's probably I think next time we'll try to do better.

C

Okay, I think. That's anything else. We wanted to discuss.

B

D

From myself, thanks just thanks again for 801.

C

B

A

Everyone thank you thank.

E

C

Okay, good night.

D

E

D