-
Notifications
You must be signed in to change notification settings - Fork 360
FIx: Ws -add guardrail to bindAsyncStart in Publisher. #7149
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
base: master
Are you sure you want to change the base?
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7149 +/- ##
==========================================
- Coverage 84.48% 84.47% -0.02%
==========================================
Files 523 523
Lines 22448 22452 +4
==========================================
+ Hits 18966 18967 +1
- Misses 3482 3485 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Overall package sizeSelf size: 4.39 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 2.0.0 | 68.46 kB | 797.03 kB | | dc-polyfill | 0.1.10 | 26.73 kB | 26.73 kB |🤖 This report was automatically generated by heaviest-objects-in-the-universe |
b7b4547 to
890fbf0
Compare
|
BridgeAR
left a comment
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.
Please also add a regression test
What does this PR do?
Adding a check to verify the span is present on the context before calling finish.
Motivation
There is a current escalation where the customer is using a long standing websocket connection and migrating traffic kubernetes pods while maintaining the same websocket. In doing so it appears the span on the context, which is the is lost and when attempting to call finish there is no longer a present span.