-
Notifications
You must be signed in to change notification settings - Fork 293
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
Fix NullReferenceException in GetBytesAsync #1906
Conversation
Codecov ReportBase: 70.79% // Head: 69.62% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #1906 +/- ##
==========================================
- Coverage 70.79% 69.62% -1.17%
==========================================
Files 292 292
Lines 61732 61732
==========================================
- Hits 43701 42983 -718
- Misses 18031 18749 +718
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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, thanks @Wraith2 for the prompt fix. I tried to re-trigger the pipeline to run the tests a few times yesterday as I'm fairly sure the failures are not due to your changes.
fixes #1903
When calling GetBytesAsyns with no timeout no cancellation token source is created. The source value is captured by the async context and is being unconditionally disposed in DisposeCore(). This fix adds a null check before disposal.
Covering test is added.
/cc @NickKerensky