Skip to content

Document and test omitted activity backoff maximum - #273

Merged
rmcdaniel merged 2 commits into
mainfrom
agent/sdk-rust/219-maximum-omission
Nov 14, 2026
Merged

rmcdaniel merged 2 commits into
mainfrom
agent/sdk-rust/219-maximum-omission

Conversation

@rmcdaniel

@rmcdaniel rmcdaniel commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

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.

@sonarqubecloud

Copy link
Copy Markdown

@rmcdaniel

Copy link
Copy Markdown
Member Author

Maintainer source review of exact 8f4d51a00c439659cc89bc1c2ae97a4b51504252: the complete change is README/API explanation plus one command/replay test. Production code, constructor defaults and emitted wire behavior are unchanged. The control checks the finite nine-attempt uncapped list through 128 seconds, replays the recorded complete list without scheduling a second command, and rejects a 60-second cap that changes the stored list. The documentation correctly distinguishes that case from a cap that leaves the encoded list identical.

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.

@rmcdaniel
rmcdaniel marked this pull request as ready for review November 14, 2026 02:37
@rmcdaniel
rmcdaniel merged commit 7325699 into main Nov 14, 2026
19 checks passed
@rmcdaniel
rmcdaniel deleted the agent/sdk-rust/219-maximum-omission branch November 14, 2026 02:37
@rmcdaniel

Copy link
Copy Markdown
Member Author

Source/main delivery: normal merge 7325699d7f09e57293d66169541d26efdd484f82, tree ca609d042ff65b84bd547b3d13099b0d316df6ff, exactly equals reviewed/tested 8f4d51a with an empty full-tree diff. The remote topic branch is absent.

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.

@rmcdaniel

Copy link
Copy Markdown
Member Author

The Docs Rust omission-explanation slice is delivered: Docs544 final receipt. Exact reviewed head c93edec53966d3c38e86497947bec3a8d3eb653d merged as cd886bd44dae58f9276199cd7258a80d00175815 with full tree equality. All 11 head checks, all 12 actual-main checks and protected Pages 43550199648 succeed. All eight public Rust guide sections across English and seven translations equal the reviewed build, including None/explicit Some(maximum), nine total attempts/eight delays through 128 seconds, finite budget/original configured deadline/overflow and full encoded-list plus other-known-field replay comparison. Canonical/v2 model projections also pass.

The public guide links accepted README source 7325699d7f09e57293d66169541d26efdd484f82 and the existing published API method. Stable API identity remains Rust 4.17/source 52208134296009bbae1af316c8efac89d3465990/crate checksum 6de774879fe8411776b60736391b2c6b426bb1bc125268718004656efd52f5c3. Selections and static artifacts are unchanged. Owned build container/remote branch are independently absent; source is clean. This delivers explanation of existing behavior, with no default, protocol, package, other-binding cap or installed timing claim. Rust retains its separate installed timing observation and General retains the remaining cross-binding #219 reconciliation/closure.

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.

1 participant