fix: honor --no-now before the first Loop run - #107
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
immediate=falsein the stable scheduler:createdAt + intervalinstead of immediate dueimmediatefield (they keep the existing immediate behavior)--no-nowdoes not dispatch before the interval and does dispatch exactly when dueWhy
README documents
--no-nowas waiting before the first run, but both the shared scheduler and V2 prompt runtime treated anylastRunAt=0job as immediately due regardless ofimmediate=false. This restores the documented behavior without changing normal/loopstartup semantics.Scope
Runtime scheduling semantics + regression tests. OpenCode 2 stable parity remains unclaimed.