fix(testing-sdk): support PENDING status reinvocation and execution failure #397
Conversation
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
ParidelPooya
approved these changes
Dec 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue #, if available:
#384
Description of changes:
When the client (language SDK) has stale data, it should be reinvoked if it exited without knowing the latest state of the checkpoint API. This is how the actual service works, and so it should be implemented in the testing library as well. This also fixes an issue where the language SDK exits at the same time that a callback completes, and hangs forever/throws an error. It will now re-invoke in this case.
Additionally, the testing SDK will now throw an error when the language SDK returns PENDING with no outstanding pending operations, timers, or stale data. This will fix the issue where it would hang forever when this happened.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.