Skip to content

fix(node): retry gateway activity after failed early reports - #453

Open
Maya-Kid wants to merge 1 commit into
deeplethe:devfrom
Maya-Kid:fix/gateway-activity-retry
Open

Maya-Kid wants to merge 1 commit into
deeplethe:devfrom
Maya-Kid:fix/gateway-activity-retry

Conversation

@Maya-Kid

Copy link
Copy Markdown

An early gateway report drained pending activity before sending it. When the master returned HTTP 503, the next regular poll could no longer report those requests.

Retain the failed batch for the next regular poll and combine it with activity that arrived during the early request. Carry a digest of the original sandbox's creation token so the master can reject activity for an older instance of a reused ID. Fresh activity still includes the legacy ID list for older masters. Retries use the instance-bound field and require an updated master to count them.

Loopback HTTP tests cover 503 recovery, concurrent activity, and a successful early send. A master API test deletes and recreates the same ID and verifies that only the current instance can update its idle clock and desired tier.

All 411 Rust tests passed on macOS. Clippy, formatting, and diff checks passed.

Signed-off-by: dada-yan <BinjunYann@gmail.com>

This branch has not been deployed

No deployments
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