Fix for lingering timer after Connection.call() has exited with an error#353
Merged
bsrdjan merged 2 commits intoSAP-archive:mainfrom Jan 8, 2024
verwema:fix/timerlingering
Merged
Fix for lingering timer after Connection.call() has exited with an error#353bsrdjan merged 2 commits intoSAP-archive:mainfrom verwema:fix/timerlingering
bsrdjan merged 2 commits intoSAP-archive:mainfrom
verwema:fix/timerlingering
Conversation
|
|
Contributor
|
Thank you @muellma-items for the fix. The case was not covered by unit tests. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Possible fix for Connection.call() timeout blocking main thread exiting, as described in #352