-
Notifications
You must be signed in to change notification settings - Fork 60
Handle notifications as retry events in the invoker #3177
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
slinkydeveloper
merged 2 commits into
restatedev:main
from
tillrohrmann:fix-invoker-retries
Apr 18, 2025
Merged
Handle notifications as retry events in the invoker #3177
slinkydeveloper
merged 2 commits into
restatedev:main
from
tillrohrmann:fix-invoker-retries
Apr 18, 2025
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
Since the retry logic also tracks notification proposals in the JournalTracker, we need to handle notifications as retry events because they can unblock a waiting for retry invocation. This commit changes the behavior accordingly.
slinkydeveloper
approved these changes
Apr 18, 2025
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.
This is correct, my previous fix solved only the is_ready_to_retry()
condition, but failed to consider that the retry timer might fire before getting the notification, so here we are.
Could you add a unit test exactly for this scenario?
- Mock the invocation in waiting to retry
- Fire the timer
- Then send the notification, and see if this triggers the retry
30 LLM calls later:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Since the retry logic also tracks notification proposals in the JournalTracker, we need to handle notifications as retry events because they can unblock a waiting for retry invocation. This commit changes the behavior accordingly.