Persister no longer treats transient errors as errors in MaybeTerminalSuccessTransition#1721
Closed
benalleng wants to merge 1 commit into
Closed
Persister no longer treats transient errors as errors in MaybeTerminalSuccessTransition#1721benalleng wants to merge 1 commit into
benalleng wants to merge 1 commit into
Conversation
bb02b0d to
e62be8b
Compare
Collaborator
Coverage Report for CI Build 29046681515Coverage decreased (-0.07%) to 85.932%Details
Uncovered Changes
Coverage Regressions2 previously-covered lines in 2 files lost coverage.
Coverage Stats
💛 - Coveralls |
7090905 to
7189410
Compare
7189410 to
592747e
Compare
Previously a transient error was treated as an error in the persister alongside fatal errors but unlike fatal errors transient errors were not giving the state at which it was reached. This commit returns the current state alongside the error while still retaining a NoOp in the persister with the expectation that the caller will want to try again.
592747e to
1c003c9
Compare
Collaborator
|
I think it is creating a bit of an anti pattern - namely that for this transition the transient error is considered a success while for all other transitions the transient error is still an error. Was there a reason you feel like for this transition it should be a success rather than an error? |
Collaborator
Author
|
This serves as a blueprint for the transition states. If we feel like we like this shape I can implement the rest the same way |
Collaborator
|
I had Fable write an alternative, more generic approach for the same concept here #1724. The first commit is the relevant one, introducing current state on all transient errors. |
Collaborator
|
Superseded by #1724 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #1709
Previously a transient error was treated as an error in the persister alongside fatal errors but unlike fatal errors transient errors were not giving the state at which it was reached.
This commit returns the current state alongside the error while still retaining a NoOp in the persister with the expectation that the caller will want to try again.
Coded with assistance from deepseek v4
Pull Request Checklist
Please confirm the following before requesting review:
AI
in the body of this PR.