Repository navigation
Fix relay delivery retries and diagnostics for RC2 - #11
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
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.
Summary
remain_countonly on success or final retry exhaustion;cleanup, retry horizon, metadata parsing, and bounded response capture.
RC1 finding corrected
RC1 production diagnostics showed that some receivers synchronously fetch
actors, keys, objects, parents, contexts, or collections before returning from
/inbox. Transient five-second delivery timeouts were terminal becauserelay-v2tasks hadRetryCount: 0. The shared payload also expired after twominutes and was decremented after each failed attempt.
RC2 keeps the existing five-second per-attempt HTTP circuit breaker but retries
the target at bounded Fibonacci delays. The delivery model remains at-least-once.
Validation
go vet ./...;git diff --check;No release tag, package publication, or deployment is performed by this PR.