Repository navigation
Document and test omitted activity backoff maximum - #273
Conversation
|
|
Maintainer source review of exact All 19 current-head checks are terminal: 17 success and two expected Server-qualification skips. Stable/MSRV Rust, format/Clippy, full corpus, Avro, package, docs, CodeQL, Sonar and target-branch qualification passed at this head. The skipped installed jobs are not timing evidence. The current README will explain the shipped behavior after merge. Stable API documentation continues to build the exact published 4.17 crate; the source comment is for the next ordinary release, without an overlay or duplicate publication. Root guide follow-through has been prepared with Docs. The separate ordinary published-package timing observation remains Rust's next acceptance item after Server#980; shared219 is not closed. |
|
Source/main delivery: normal merge All five actual-main workflows are terminal success: CI43547308659, Public Boundary43547308631, CodeQL/Push43547307972, Sonar43547308633 and API Docs43547308636. The published-stable documentation build still binds the released 4.17 crate/source522; no source overlay or new tag/package was introduced. The accepted README and source control complete Rust's omission explanation/control portion. Root guide/locales follow-through is with Docs. The separately named published-package repeat-last timing observation remains after Server#980, so the shared issue stays open. |
|
The Docs Rust omission-explanation slice is delivered: Docs544 final receipt. Exact reviewed head The public guide links accepted README source |



Rust's generated retry policy already treats maximum_interval=None as uncapped. Explain the omission explicitly in the README/API source and prove the nine-attempt1..128s schedule, unchanged recorded-policy replay, and rejection when a60-second cap changes the stored list. Production behavior, defaults and wire fields are unchanged. Addresses the Rust explanation/control portion of durable-workflow/.github#219.
Validation: all19 exact-head checks terminal (17 success/two expected Server skips); all five actual-main workflows succeed at merge7325699d, whose tree equals reviewed8f4 exactly. Topic branch is absent. Stable API documentation still uses the verified published4.17 crate; the new API source comment will appear in the next ordinary release. Root-guide follow-through is Docs#544. A separately named published-package repeat-last timing observation remains after Server#980; no duplicate SDK release or shared-issue closure is selected.