Remove terminal_error method for sender and receiver#1123
Remove terminal_error method for sender and receiver#1123arminsabouri merged 1 commit intopayjoin:masterfrom
Conversation
Pull Request Test Coverage Report for Build 18223941555Details
💛 - Coveralls |
|
Blocked by #1132 |
49dda72 to
2b66380
Compare
2b66380 to
a380dc0
Compare
44d98bd to
47ebcd1
Compare
arminsabouri
left a comment
There was a problem hiding this comment.
Approach Ack 🔥
What else needs to be done for this to come out of draft?
|
looks like squashing the commits, but that could be done w squash and merge |
|
Sorry, stepped off before I marked it ready for review, I would like a definitive decision on whether to return only as an Ok resultand expect vs accepting errors as the 2 fixup commits take opposite approaches on the cli and test respectively, so deciding which to settle on before squashing them, but then this is ready to go. |
47ebcd1 to
ef9c579
Compare
| .map(|e| e.to_json().to_string()), | ||
| }; | ||
| recv_rows.push(row); | ||
| match replay_receiver_event_log(&persister) { |
There was a problem hiding this comment.
Any reason we wouldnt match on a error for the active sessions? They can also expire and throw
There was a problem hiding this comment.
Matched to errors on active sessions too now, but the completed_at field remains None on an error in these cases.
The public `terminal_error` method does not really serve a purpose as we now deal with errors directly in the state machine and don't really have an opportunity to call the `terminal_error` method where looking for an error wouldn't be sufficient.
ef9c579 to
47bdef2
Compare
The public
terminal_errormethod does not really serve a purpose as we now deal with errors directly in the state machine and don't really have an opportunity to call theterminal_errormethod where looking for an error wouldn't be sufficient.Closes #1118
Pull Request Checklist
Please confirm the following before requesting review:
AI
in the body of this PR.