-
-
Notifications
You must be signed in to change notification settings - Fork 725
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
fix(start): discard steam controller errors when closed #3161
Open
phryneas
wants to merge
2
commits into
TanStack:main
Choose a base branch
from
phryneas:pr/try-controller
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.
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
phryneas
commented
Jan 14, 2025
Comment on lines
+153
to
+156
// controller = { | ||
// enqueue: chunk => { try { c.enqueue(chunk); } catch {} }, | ||
// close: () => { try { c.close(); } catch {} }, | ||
// } |
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.
Doing this here seems to be the place that is the most defensive - anywhere "further out", it could swallow errors e.g. if controller
is still undefined etc.
phryneas
added a commit
to apollographql/apollo-client-nextjs
that referenced
this pull request
Jan 14, 2025
View your CI Pipeline Execution ↗ for commit 92b9a63.
☁️ Nx Cloud last updated this comment at |
SeanCassiere
changed the title
Stream Controller: try enqueue/close without throwing error
fix(start): discard steam controller errors when closed
Jan 15, 2025
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.
Stream Controller: try enqueue/close without throwing error
Both
controller.enqueue
andcontroller.close
throw an error if the stream has already been closed.This could be the case because the reading side just doesn't have interest in more incoming values and has closed the stream on the reading side.
Up until now, this would cause an error to be thrown on the console once more chunks or a close request were streamed in.
This wraps
.close
and.enqueue
in atry..catch
block and disregards the result.Reading the standard I don't see any possible other reasons for an error to be thrown, so this should be fine.