-
-
Notifications
You must be signed in to change notification settings - Fork 126
fix(client): preserve recipient in <ack>, soften unknown stream:error #633
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
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
e8c8ed7
Improve stream error handling and ACK node attributes
zdanysfa 2db09cf
Merge branch 'oxidezap:main' into fix-recipient-ack
zdanysfa d35c51a
Refactor stream error handling logic
zdanysfa 1ab104b
Improve comments and add test for encode_ack_bytes
zdanysfa 895dc72
refactor(stream-error): consolidate is_logged_in clear, clarify diver…
jlucaso1 4c7acf5
fix(stream-error): clear is_logged_in on 429/503, downgrade unknown t…
jlucaso1 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keep
429and503visible viaEvent::StreamError.These branches changed the teardown behavior, but they also stopped surfacing a structured stream-error event. That makes rate-limit and service-unavailable rejections invisible to consumers exactly in the cases where the transport is intentionally left alive for the socket layer to finish the shutdown.
Suggested fix
"429" => { // Server signalled rate-limit on this session: mark logged-out so // outgoing sends bail fast instead of being interpreted as abuse // while we wait for the (likely-imminent) reconnect. warn!( "Got 429 stream error (rate limited). Will auto-reconnect with extended backoff." ); self.is_logged_in.store(false, Ordering::Relaxed); + self.core.event_bus.dispatch(Event::StreamError( + crate::types::events::StreamError { + code: code.to_string(), + raw: Some(node.to_owned()), + }, + )); self.auto_reconnect_errors.fetch_add(5, Ordering::Relaxed); } "503" => { // Server is going down/restarting: mark logged-out so sends fail // fast against the soon-to-die socket. Auto-reconnect handles recovery. info!("Got 503 service unavailable, will auto-reconnect."); self.is_logged_in.store(false, Ordering::Relaxed); + self.core.event_bus.dispatch(Event::StreamError( + crate::types::events::StreamError { + code: code.to_string(), + raw: Some(node.to_owned()), + }, + )); }📝 Committable suggestion
🤖 Prompt for AI Agents