Skip to content

Conversation

@ceedubs
Copy link
Contributor

@ceedubs ceedubs commented Feb 2, 2026

I just ran into the same issue described in #211. In my case I had noticed the note about calling Stream.close in the rejectRequest docs but I didn't realize that the disclaimer applied to rejectRequestWith as well. Based on this comment maybe it makes sense to close the underlying stream when rejecting the request, but short of that maybe this note will help someone else avoid the same issue.

I just ran into the same issue described in [jaspervdj#211](jaspervdj#211). In my case I had noticed the note about calling `Stream.close` in the `rejectRequest` docs but I didn't realize that the disclaimer applied to `rejectRequestWith` as well. Based on [this comment](jaspervdj#211 (comment)) maybe it makes sense to close the underlying stream when rejecting the request, but short of that maybe this note will help someone else avoid the same issue.
@jaspervdj
Copy link
Owner

Thank you!

@jaspervdj jaspervdj merged commit bfa5fe5 into jaspervdj:master Feb 3, 2026
@ceedubs ceedubs deleted the close-connection-note branch February 3, 2026 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants