Skip to content

Prepare native fired-timer redrive and fractional-clock guidance - #541

Draft
rmcdaniel wants to merge 2 commits into
mainfrom
agent/durable-workflow-github-io/native-timer-redrive
Draft

rmcdaniel wants to merge 2 commits into
mainfrom
agent/durable-workflow-github-io/native-timer-redrive

Conversation

@rmcdaniel

Copy link
Copy Markdown
Member

Prepare bounded English guidance for the accepted native plain-timer redrive and fractional replay-clock correction. The Service Mode API reference explains the complete ordered timer pair, one fresh shared successor ID, no new timer row/task, original clock and immediate-predecessor lineage across repeated redrive, full initial/event clock authorities and retained historical rounding. Existing refusal limits and separate actual cold-worker qualification remain explicit.

The native paragraph in failures/recovery now distinguishes published 3.8–3.10 behavior from the pending source correction and links to the detailed Service Mode contract. Embedded redrive guidance and all executable examples are unchanged.

Source: accepted Server #1215 / 5221ed82, draft 3.11 release preparation #1218, and the full-precision installed cohort requirement. Existing Server #980 owns the producer/SDK outcome; Core's #992 precision/reference follow-through remains separate. Source tests do not qualify a published producer or an SDK Worker, and lost fractions cannot be reconstructed.

The selected Server 3.10.0 / Chart 2.0.0 pair, manifest, installers, protocol/OpenAPI and catalog files remain unchanged. No image digest or runtime is selected. Version/source prose is explicitly pending publication and consumer qualification.

This is the requested English semantic-review draft at 9f21e54a2e4b65ac9a9e302fafadb70f12d62c00. Whitespace, unchanged executable-block/artifact checks and public-boundary checks pass. No local build or runtime experiment ran. All seven translations/source hashes, ordinary locale/link review, current required CI, final bounded build and deployment/public readback remain later gates. Release wording and stable selection wait the actual qualified producer, applicable published PHP/Python/Rust cold-worker receipts and Chart OCI receipt; Core follow-through stays separately attributed. No generic #980 closure is inferred. Draft #534 remains separately held.

@sonarqubecloud

Copy link
Copy Markdown

@rmcdaniel

Copy link
Copy Markdown
Member Author

Bounded producer-semantic review PASS for the two English deltas at exact 9f21e54a2e4b65ac9a9e302fafadb70f12d62c00.

The API reference matches accepted Server 5221ed82 and reviewed release preparation 8d7ffd2e: one complete ordered plain pair at a unique pre-failure step, one new shared timer ID, zero successor timer rows/tasks, unchanged source history, and only the failed activity resumed. The refusal table correctly distinguishes unsupported timer metadata from missing/reversed/duplicate/mismatched pair data; cancelled timers and the existing structural/fingerprint/external-payload/service-upsert limits retain their prior boundaries.

Clock authority and precision are correct. Consumed steps use their original event times, the initial anchor uses persisted run start, repeated redrive preserves existing clock strings, and historical lost fractions cannot be reconstructed. This does not add ordinary-entry clock support or assert a new SDK release is needed.

I also checked the historical native claim against exact published tags 3.8.0, 3.9.1, 3.9.2 and 3.10.0. All four have the identical redrive blob 3a60fd2340b2dea057a38c05c8c2cbfddf1839c2, including retained-string precedence, whole-second first-reuse fallback and the earlier timer refusal. Removing the former blanket fractional-clock equality implication is accurate. Core precision/reference follow-through remains separately attributed.

The pending-publication callout and unchanged selected pair correctly distinguish source acceptance from an actual qualified producer/SDK/Chart tuple. Complete PR file inventory is only these two English documents, so selectors, installers, OpenAPI and catalog are unchanged by this head. This is source prose review; translation, final producer/Chart receipt binding, build/deployment and live readback remain later gates. No installed or cross-mode acceptance is inherited.

This branch has not been deployed

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant