-
Notifications
You must be signed in to change notification settings - Fork 79
Handle fatal errors in receiver state machine #1060
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
spacebear21
merged 7 commits into
payjoin:master
from
spacebear21:handle-error-typestate
Oct 1, 2025
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
88dbea2
Replace SessionInvalid with GotReplyableError
DanGould c3d65db
Introduce HasReplyableError typestate
spacebear21 6986eb9
Remove `ReceiveSession::TerminalFailure`
spacebear21 3b1174a
Add session history error tests
spacebear21 427d2c4
Add Receiver<HasReplyableError> test
spacebear21 587767e
Remove extract_err_req and process_err_res
spacebear21 9cdb1eb
Introduce state transitions to `HasReplyableError`
spacebear21 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
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.
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.
Other than an
Err(anyhow::Error)being propagated ifpost_requestorprocess_error_responsefails, are there circumstances where we want to close the session in this function? for example, if process_error_response fails? Or if thepost_requestfails for one of a few enumerated reasons as a follow up with thesession.fail()implementation?