[codex] Restore preparation timers from action events#577
Merged
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
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.
Summary
startedAtand userPreparation Action Events instead of relying on suspended timer ticks.Root Cause
Dart timer ticks can stop while the phone sleeps, and the old restoration path depended on elapsed snapshots. After schedule start, backend frozen preparation can also change step IDs/fingerprints, which caused local run snapshots and skip actions to be discarded.
Validation
dart run build_runner build --delete-conflicting-outputsflutter analyzeflutter test test/presentation/app/bloc/schedule/schedule_bloc_test.dartflutter testgit diff --check