Repository navigation
fix(individuality): subscribe a watch again after its subscription fails #442
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
Open
BigTava
wants to merge
1
commit into
main
Choose a base branch
from
fix/individuality-watch-resubscribe
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
12 changes: 12 additions & 0 deletions
12
product-sdk/pending-changesets/individuality-watch-resubscribe.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| --- | ||
| "@parity/product-sdk-individuality": minor | ||
| "@parity/product-sdk": minor | ||
| --- | ||
|
|
||
| `watchCurrentGame`, `watchPlayer` and `watchParticipant` now subscribe again | ||
| after a failed subscription instead of ending. PAPI ends a `watchValue` on its | ||
| first failed query, so one lost or failed host answer used to silence the watch | ||
| for good. The failure still goes to `onError`, and the watch subscribes again | ||
| after a wait that doubles from one second to thirty and drops back to one second | ||
| once a value arrives. A value that matches the last one delivered is not | ||
| delivered again after the watch resubscribes. |
Oops, something went wrong.
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.
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.
We never unsubscribe the errored subscription before retrying, so this only holds if PAPI tears the stream down on error. I'd call subscription?.unsubscribe() here to be safe, and the fake can't catch a leak since it shares one unsubscribe across subscribes.