-
Notifications
You must be signed in to change notification settings - Fork 492
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
refactor(iot-device): Add additional logging statement to disposal flow #2414
Conversation
abhipsaMisra
commented
May 25, 2022
bcc3aaa
to
bf5b699
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
b3d5c8b
to
f41e286
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
} | ||
if (Logging.IsEnabled) | ||
{ | ||
Logging.Enter(this, $"{nameof(DefaultDelegatingHandler)}.Disposed={_disposed}; disposing={disposing}", $"{nameof(TransportHandler)}.{nameof(Dispose)}"); |
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.
Why DefaultDelegatingHandler
?
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.
The _disposed
parameter referenced throughout our delegating handler pipeline is actually the protected variable defined in DefaultDelegatingHandler
:
protected volatile bool _disposed; |
This, along with the way base.Dispose()
and inherited.Dispose()
are mixed in our pipeline disposal flow is something I'm looking to refactor.
* refactor(e2e-tests): Update provisioning tests to retry on throttling (#2411) * refactor(e2e-tests): Update reprovisioning tests to retry on throttling * refactor(iot-device): Add additional logging statement to disposal flow (#2414) * fix(iot-device): Fix twin operations with Mqtt to retry on throttling (#2416) * Add documentation about HttpClient and socket exhaustion to service clients (#2423) Co-authored-by: Abhipsa Misra <[email protected]> Co-authored-by: brycewang-microsoft <[email protected]>