feat: introduce additional checks when attempting to send to bounded channels #5941
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
jstuczyn
force-pushed
the
bugfix/additional-shutdown-checks
branch
from
aba7d25 to
e981e33
Compare
…channels or to a fallible gateway
jstuczyn
force-pushed
the
bugfix/additional-shutdown-checks
branch
from
c60ed10 to
057e4ce
Compare
tommyv1987
approved these changes
Aug 11, 2025
pronebird
approved these changes
Aug 11, 2025
jstuczyn
added a commit
that referenced
this pull request
Aug 11, 2025
…channels (#5941) * feat: introduce additional checks when attempting to send to bounded channels or to a fallible gateway * return error rather than panic when merging socket during shutdown
1 task
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.
(or to a fallible gateway)
hopefully should resolve NET-538 / VPN-3782
I imagine it might have to be cherry-picked to some patched emmental branch
This change is