feat(controller-peers-env-fallback): route the controller's two identity loops through the shared lookup (task 2.1)
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
241ed3a142
commit
7a90af089c
3 changed files with 145 additions and 22 deletions
|
|
@ -22,7 +22,7 @@
|
|||
- Done when, after `/xce-build` (controller, scheduler, worker, harness) on a machine with no local cluster, the script runs with no cases and exits 0, and exits non-zero with the pre-flight message while a listener is bound to port 9990 or when pointed at a build directory missing a binary
|
||||
|
||||
- [ ] 2. Controller
|
||||
- [ ] 2.1 Route the controller's two existing identity loops through the shared lookup
|
||||
- [x] 2.1 Route the controller's two existing identity loops through the shared lookup
|
||||
- Replace the loop that picks the controller's election priority, keeping the existing "at least one candidate" guard so a standalone controller still gets priority 0, and keeping "no match gives the last index" at that call site
|
||||
- Replace the loop that picks the listen port, keeping the existing "no match with a peers list refuses to start" and "port 0 falls back to the default port" behavior
|
||||
- Pure refactor: no behavior change for any input
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue