Implement automatic retry of watch streams that terminate without any error #158
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
…due to server-side request GC) #157
tintoy
added
enhancement
Merged
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.
KubeResourceClient.ObserveEventsandKubeResourceClient.ObserveEventsDynamicnow automatically retry the underlying HTTP request if it completes without error (which it shouldn't do unless the connection has been somehow garbage-collected, server-side). Requests that result in exceptions will still be surfaced viaIObserver<T>.OnError.Note: this change has required the library to target
netstandard2.0(was previously targetingnetstandard1.4). Given the age ofnetstandard1.4, this seems unlikely to affect most consumers.Relates to #157