fix: ConnectionMonitor is stopped by cancellation token during discon… #251
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Refactored
ConnectionMonitorThreadfrom aThreadto aTaskto support proper async execution and cancellation. Updated related logic to use aCancellationToken, and replacedThread.SleepwithTask.Delay. Updated tests accordingly and added a new test to verify that the connection monitor task stops correctly after disconnect.This will stop the
ConnectionMonitorThreadfrom running forever after a disconnect.Related Issue
#246
Type of Change
Checklist
rake test)