You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the gRPC choreographer we need to provide the port number twice in order to connect to comet. Otherwise things fail silently. For eg: comet --identity IP_ADDR:50001 --port 50001 works like a charm.
However, when running with comet --identity IP_ADDR --port 50001 fails silently.
Looking at the debug logs with RUST_LOG=debug the computation outputs seem to be empty when comet is ran using the second version and we see no trace of error.
The text was updated successfully, but these errors were encountered:
rdragos
changed the title
Comet needs port number in the address as well
Comet needs port number in the address
Jun 15, 2022
When running the gRPC choreographer we need to provide the port number twice in order to connect to
comet
. Otherwise things fail silently. For eg:comet --identity IP_ADDR:50001 --port 50001
works like a charm.However, when running with
comet --identity IP_ADDR --port 50001
fails silently.Looking at the debug logs with
RUST_LOG=debug
the computation outputs seem to be empty when comet is ran using the second version and we see no trace of error.The text was updated successfully, but these errors were encountered: