Skip to content

fix(sse): the server's own error event ends the stream - #296

Merged
jfrench9 merged 1 commit into
mainfrom
bugfix/sse-server-error-is-final
Nov 13, 2026
Merged

jfrench9 merged 1 commit into
mainfrom
bugfix/sse-server-error-is-final

Conversation

@jfrench9

Copy link
Copy Markdown
Member

Summary

The server's own error event ends an operation stream. Before, the event counted as progress and reset the reconnect budget, so a stream the server answered with event: error (the per-user connection cap, a stream it refuses) was reopened without limit, and a monitor_operation call with no timeout never returned a verdict. The TypeScript client already treats the event as final.

Changes

  • robosystems_client/clients/sse_client.py: SSEClient and AsyncSSEClient close on the server's error event, as they do on the operation's own terminal events. The event is still delivered to error listeners first.
  • tests/test_sse_client.py: one connect, the error delivered, no reconnect, for both clients.

Breaking Changes

None. A patch release.

Testing

just test-all equivalent locally: ruff, format, basedpyright clean; 750 passed.

🤖 Generated with Claude Code

A stream answered with `event: error` was reopened without limit, since the
event counted as progress; a caller with no timeout never got a verdict.
@jfrench9
jfrench9 merged commit 25c1a35 into main Nov 13, 2026
6 checks passed
@jfrench9
jfrench9 deleted the bugfix/sse-server-error-is-final branch November 13, 2026 08:00
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