Bind draining payload upload retries to the current completion lease - #41
Merged
Conversation
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
2 participants
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.
Companion to durable-workflow/server#146 and durable-workflow/server#147.
Ordinary uploads are unchanged. On a draining refusal and exact advertised capability, retry identical bytes bound to the current worker completion's task, attempt, owner and payload slot. Older runtimes, client inputs and hard fences do not receive this exception.
Reuse existing worker admission waits, preserve prepared bytes and try ordinary admission again after capacity recovers. No added coordinator or handler re-execution. Prepare Rust SDK 2.0.5.
Validation on Rust 1.86: formatting passed; all-target/all-feature tests passed (211 library and 23 integration/compile tests); 3 documentation tests also passed. Sixteen upload tests cover protocol payload slots, capability rejection, fencing, stale ownership and identical-byte recovery. Full public CI passed at 7db1f87.
Real HTTP activity/workflow/query completions and cold payload readback passed with all three SDKs: durable-workflow/server#147 (comment)
Release-metadata CI is running at the final head. Published-artifact bounded-storage qualification remains on Server #146; no production deployment is claimed.