Repository navigation
Conversation
Author
|
Fixed in #2916. |
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.
Sequential
DurableClock.sleepcalls on the Durable Object engine back off as if they were failing. Each clock → run hop inherits the alarm attempts of the pass that scheduled it, so the retry delay doubles per hop and atmaxAttemptsthe execution parks for an hour (#2801).The clock schedule and the wake-up after a completed deferred now pass the row count of the engine's append-only journal tables as
progress, whichAlarmCallbackalready treats as progress. Start, resume and interrupt keep their unconditional wake-up, and a pass that fails before writing a journal row still spends the retry budget.Fixes #2801
Written with AI help (Claude Opus 5.5, OpenAI Sol 6.1, OpenAI Astra 6).