Preserve due-schedule timestamp precision - #506
Merged
Conversation
rmcdaniel
marked this pull request as ready for review
September 9, 2026 23:12
Member
Author
|
Local verification is complete for SQLite: 89 schedule, degraded-mode and command cases / 452 assertions pass, and full The first broad local command used a synchronous queue, which is deliberately unsupported by four degraded-mode cases. Rerunning with the asynchronous database queue resolved those harness errors without changing tests or product code. Existing CI remains the public MySQL gate; PostgreSQL qualification and published-artifact follow-through remain outstanding. |
This was referenced Sep 9, 2026
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
Refs #505. Preserve the
WorkflowSchedulemodel's microsecond serialization in the due-schedule predicate, instead of letting the connection format a DateTime binding at whole-second precision. No API, schema, cron or overlap-policy change.The regression persists and reloads the deadline, freezes time at exact whole-second/fractional boundaries, checks original occurrence identity, forbids early dispatch and verifies that a repeated tick does not start twice. Existing fairness checks are unchanged.
Validation
Release Follow-Through
Keep #505 open until publication and affected-consumer qualification. Inspect Server's locked Workflow/image contents and embedded consumers; SDK/CLI protocol and packages are unchanged. Run the published schedule cases on SQLite/MySQL/PostgreSQL after publication; record downstream rebuild/release decisions rather than assuming a library tag changes existing images.