Gateway standalone mode startup and identity bugs
Cluster 128600. Data as of
Nothing open on GitHub. Fix merged in #130522 on 1 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #130522. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #130522. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address bugs in the gateway's standalone startup behavior, including issues with host rendezvous process identity stability and conflicts when multiple standalone profiles attempt to coexist.
Open issues0
Open PRs0
Fixes on record
-
#130522 fix(gateway): two gateway.standalone profiles can run side by side again, including after a WSL clock resync (#128600, salvage #128602 #129035)
files:
gateway/host_rendezvous.py,gateway/run.py,tests/gateway/test_host_gateway_lock_refusal.py,tests/gateway/test_host_rendezvous.py
2 PRs closed without merging
From the close comments: merged via another change 2
Closed issues · 1
- Closed#128600[Bug]: Two `gateway.standalone: true` profiles cannot coexist — the second one is refused on the lock-loss recheck ("starting beside" then "Refusing" 2 ms later)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #130522
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 1 Oct 2026