Fix missed service notifications on all resource unregistrations #28
Conversation
This file contains 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
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.
It seems we had the different paths for handling different kind of I/O errors just due to historical reasons. Each of this paths were modified independently in different commits; originally in the case of I/O error we were not disconnecting and just notifying of it the service, letting the service to decide whether a disconnect is needed. Later, we has dropped this notification (probably deciding that the service can't do much in that case) and defaulted to unregistering the resource - but without notifying the service.
This PR brings both cases into a single one, ensuring that (1) we always disconnect on all errors and (2) we always notify the service about the disconnect.