Neil 3d9be7c269 relay: an edge fence refused as a same-epoch conflict goes once more one epoch above (#40946) ...

At 1% the edge answered fences 'conflict': it holds the fence's own epoch for another placement
(a move onto the edge whose push landed though the director counted it failed, then a placement
elsewhere minted the same epoch). Retries go to the host's current row at that same epoch, so they
kept failing until the host moved again; meanwhile the edge object claims the host and its phones
get HOST_OFFLINE instead of re-resolving. No later move can produce a same-epoch conflict (it would
answer stale), so the fence now goes once more one epoch above, which lands; a later move onto the
edge re-mints above it. Stale answers are never bumped.

2026-11-10 16:58:38 -08:00

..

src

relay: an edge fence refused as a same-epoch conflict goes once more one epoch above (#40946)

2026-11-10 16:58:38 -08:00

Dockerfile

fix(cloud): patch relay, push and connector images to Node 24.22.2 and current Alpine fixes (#36560)

2026-10-30 20:53:22 -07:00

package.json

chore(deps): apply reviewed maintenance updates and record full audit (#32349)

2026-10-23 15:14:57 -07:00

tsconfig.build.json

feat(relay): correct regional placement only when the source is idle (#20105)

2026-09-11 14:25:10 -04:00

tsconfig.json

chore(cloud): add the relay fence broker, ops console, Terraform root, scripts, and 24 cloud-* workflows (#18413)

2026-09-03 06:55:14 -04:00

vitest.config.ts

refactor(cloud): group relay assignment headroom modules (#36665)

2026-10-31 04:04:04 -07:00