macOS: all blueprints fail at startup — first coordinator→worker RPC (set_transport) times out on current main #3331
kumarganduri
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Environment: macOS 26.5 (Apple silicon), Python 3.12, install via uv,
transport default (zenoh). No robot attached.
Symptom: any
dimos run/dimos --replay runfails ~2 min after moduledeployment with:
(The module name is whichever gets the first set_transport call.) All modules
deploy fine; zero
Transport module=...log lines appear, so nocoordinator->worker RPC ever completes. Worker processes stay alive and log
nothing.
Repro:
Bisect evidence (same machine, same command):
29f35555(mid-July)7d301af5(current main)Suspected cause: #3176 ("Replace RPC with native Zenoh RPC", DIM-1145) is
in the window, together with the
eclipse-zenoh >=1.0->>=1.9bump. Thenew-main runs also print a zenoh warning the old base never showed, which
smells like peer discovery not connecting coordinator and workers on macOS:
Calling
set_transportdirectly on a module instance in-process works fine,so this looks confined to the RPC path between processes.
Happy to test candidate fixes or gather more logs from this machine — macOS
may just not be covered by CI for this path.
All reactions