Skip to content

fix: later sends get ReceiverClosed too after the remote receiver is dropped - #134

Closed
rklaehn wants to merge 3 commits into
rklaehn/remote-receiver-closedfrom
rklaehn/remember-receiver-closed
Closed

rklaehn wants to merge 3 commits into
rklaehn/remote-receiver-closedfrom
rklaehn/remember-receiver-closed

Conversation

@rklaehn

@rklaehn rklaehn commented Oct 9, 2026

Copy link
Copy Markdown
Collaborator

Based on #133.

After the first error, a remote sender is closed and every later send gets Io(BrokenPipe). So with #133 only the first send sees ReceiverClosed, and a clone that didn't hit the stop itself never does.

This remembers whether the sender closed because of a Stopped(0). Only then do later sends get ReceiverClosed. All other errors, and cancelled sends, still give BrokenPipe.

@Frando

Frando commented Oct 9, 2026

Copy link
Copy Markdown
Member

This was merged manually into #130 and github fails to detect it as merged, thus closing.

@Frando Frando closed this Oct 9, 2026
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