-
Notifications
You must be signed in to change notification settings - Fork 299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: fix naming, order and formatting for diagnostics #1637
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1637 +/- ##
==========================================
+ Coverage 71.30% 71.32% +0.02%
==========================================
Files 295 295
Lines 61195 61205 +10
==========================================
+ Hits 43637 43657 +20
+ Misses 17558 17548 -10
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
@Wraith2 Running tests now |
@Wraith2 Works great! No exceptions after over 500k requests. |
Over 5 million requests now without exceptions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes #1634
We were not being consistent about calling diagnostic message output functions before we set the result/exception/cancel methods on the TaskCompletionSource that the users is waiting on. This allowed a rare race condition to occur in libraries consuming diagnostic events and attempting to correlate it to their own current context.
This PR does 3 things:
s_diagnosticListener
not_diagnosticListener
N.B. netfx does not use diagnostics so no changes are required for that part of the project.
/cc @okolvik-avento if possible you could try the output artifacts nuget package once the CI run has completed?