toidiu
toidiu
I am noticing that version 1.35 makes 1 req/repo. Version 1.39 makes (1 req/ PR in repo) + (1 req/ PR in repo if there is a comment on the...
@bjoernhaeuser that diagnosis was for polling only. We are in the process of switching to hooks now(we had to jump thru some hoops because our Jenkins setup is in a...
Thanks for the explanation. The intention of frame_processed makes sense but there is text that added to my confusion. There might still be a good usecase for frame_sent/recv event and...
> All the tooling also utilizes this. Splitting this up by default would mean lots of code churn (one of the reasons we added a separate frames_processed in the first...
Hi, wanted to make sure someone saw the above comment. Would be good to know which way the draft design will lean so that we can remain compatible.
> For now, I'd say the best approach is to log two packet_* events then (as those should be easy to merge automatically by tooling). Thanks @rmarx for the reply...
Hi @Hadatko not sure I fully understand the issue and how to repro it. Are you building `aws-c-cal` (with USE_OPENSSL) and also manually building `s2n-tls`? Or are you only building...
Can you share how to repro the testing and results above
ossl3 support has been added: https://github.com/aws/s2n-tls/issues/3442
ossl3 support has been added: https://github.com/aws/s2n-tls/issues/3442