Skip to content

Correctly propagate errors in NetworkTransport receive stream #4

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

Merged
merged 1 commit into from
Mar 4, 2025

Conversation

mattt
Copy link
Contributor

@mattt mattt commented Mar 4, 2025

Replaces AsyncStream with AsyncThrowingStream to ensure network errors are correctly propagated to callers. Updates receive() to handle errors from the underlying message stream.

Changes AsyncStream to AsyncThrowingStream to ensure network errors are correctly propagated to callers. Updates receive() to handle errors from the underlying message stream.
@mattt mattt changed the title Properly propagate errors in NetworkTransport receive stream Correctly propagate errors in NetworkTransport receive stream Mar 4, 2025
@mattt mattt merged commit b761d3e into main Mar 4, 2025
1 check passed
@mattt mattt deleted the mattt/fix-network-transport branch March 4, 2025 14:05
devyhan pushed a commit to devyhan/swift-sdk that referenced this pull request Apr 4, 2025
…ntextprotocol#4)

Changes AsyncStream to AsyncThrowingStream to ensure network errors are correctly propagated to callers. Updates receive() to handle errors from the underlying message stream.
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.

1 participant