Repository navigation
docs: explain whole-second activity retry intervals - #124
Merged
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.
Changes
Part of durable-workflow/durable-workflow.github.io#361. Document whole-second
rounding at ActivityRetryPolicy::backoff_intervals and exponential_backoff.
Positive fractional Durations round up; a maximum is applied before conversion.
Zero remains zero. This durable policy is separate from HTTP transport retries.
Only rustdoc comments change. Runtime, dependencies, package version and wire
format remain unchanged. Seventeen candidate checks pass with two explicit
worker-qualification skips and zero OPEN/CONFIRMED Sonar findings. Normally
merged as
72aa2810, preserving qualified tree20d7d069. Documentation run39887556469 passes. Both actual public builder-method references show the
new conversion documentation. No crate release is required or claimed.