Skip to content

Document fixed workflow-start time and durable wait patterns - #169

Merged
rmcdaniel merged 1 commit into
mainfrom
docs/fixed-workflow-start-clock
Oct 20, 2026
Merged

rmcdaniel merged 1 commit into
mainfrom
docs/fixed-workflow-start-clock

Conversation

@rmcdaniel

@rmcdaniel rmcdaniel commented Oct 20, 2026 •

Copy link
Copy Markdown
Member

Change

Interim released-behavior clarification for shared #215, alongside Website #307. Website #302 has been superseded by the actual advancing replay-safe clock requirement.

Document Python 2.6.1's current fixed run-start ctx.now(), successor-run anchors, persisted timestamp precedence, missing-clock diagnostics, durable timers/Server deadlines and sequence-based event ordering. Preserve the currently released #146 behavior in this docs-only PR; #215 owns the new advancing clock and replay-compatible migration.

Only docs/sdk-reference.md changes. No runtime, dependency, protocol or version change, and no claim of normalized cross-SDK clocks.

Verification

  • Normal PyPI Python 2.6.1; loaded workflow SHA-256 a28a4b585269ccca2643cf0a8dd82ae6a4800625a53ffa1940c5e85df12865aa matches the immutable release.
  • The example and seven constructed-history controls pass in each of two independent replay processes, including timer scheduling, fixed clock after timer completion, replay/input immutability, successor anchor and invalid/missing clock diagnostics.
  • Example matches Website #307. No live Server timing comparison is claimed.

General retains merge and portal-publication acceptance. Publishing this clarification does not complete shared #215.

@sonarqubecloud

Copy link
Copy Markdown

@rmcdaniel

rmcdaniel commented Oct 20, 2026 •

Copy link
Copy Markdown
Member Author

Published portal acceptance is now verified for this interim documentation correction.

  • Merged source 412a10f / tree 71f8ab19800e34eb003d03f1989bda77fe5cd98d; only docs/sdk-reference.md changed. The remote head docs/fixed-workflow-start-clock is retired (exact ref returns 404).
  • Normal portal run 39399839289 passed build and deployment; deployment completed 2026-10-20 10:13:42 UTC.
  • Live deployment audit identifies that exact merged source and SDK 2.6.1. The live SDK reference contains WaitWithoutClockLoop, the persisted start-time contract and the separate monotonic-clock guidance.
  • Final verification 2026-10-20 10:41:22 UTC: all 15 exact-main check runs PASS, including CI 39399839051, all Python versions, integration, regression corpus, package, lint, advisory throughput, target-branch qualification, Sonar and boundary. The live audit still matches that exact merged source.

This documents the currently released fixed-start behavior. It does not deliver an advancing replay clock: .github #215 remains OPEN, and Website #302 remains superseded by that product feature.

No new runtime or qualification phase was needed; all task runtime/dependency/raw state remains retired.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants