Fix resubscribing after GraphQL subscription finished by server#1368
Merged
tyranron merged 5 commits intographql-rust:masterfrom Mar 5, 2026
Merged
Conversation
Contributor
Author
FCMFix resubscribing in graphql-transport-ws protocol (#1368) |
Contributor
Author
|
@tyranron Found that problem is related to |
Contributor
Author
|
@tyranron |
50U10FCA7
changed the title
graphql-transport-ws protocol
tyranron
added
enhancement
tyranron
approved these changes
Mar 5, 2026
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.
Synopsis
Current
graphql-transport-wsimplementation (andgraphql-wstoo) doesn't allow to resubscribe to sameidafter subscription was completed by server.Solution
Retain
stoppersremoving the completed ones before checking whether user can subscribe toid.Checklist