fix(converter): handle serialization of recursive exceptions #696
Conversation
This file contains 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
|
|
yunmanger1
force-pushed
the
fix-recursive-error-serialization
branch
from
4e4f84a to
1ec3f62
Compare
It is kind of an easy mistake to do in python:
```
try:
raise ValueError("test")
except Exception as e:
raise e from e
```
The reraised exception will have e.__cause__ referencing itself resulting in failure to serialize error and python sdk won't report anything resulting in retries and startToClose timeouts.
yunmanger1
force-pushed
the
fix-recursive-error-serialization
branch
from
1ec3f62 to
f1dd820
Compare
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.
Handle edge case of recursive exceptions in failure converter.
Why?
It is kind of an easy mistake to do in python:
The re-raised exception will have
e.__cause__referencing itself resulting in failure to serialize error and python sdk won't report anything resulting in retries and startToClose timeouts.