Notice that we have 3 port listening, where just 1 was expected. If we keep doing advances like this, eventually it will exhaust all available ports on the host (about 65535).
Expected behavior
After every advance, jsonrpc-remote-cartesi-machine should keep listening only in one port, instead of multiple ports.
Preferably in the same initial port 8000. If it's not the same port, the cli must return the next port the user can connect to, this could be optional and saved to a file, although I dislike this port changing behavior (at least in the cli).
Use case
The idea here is to be able to implement a rudimentary "node" using just the cli to perform advance/inspect states to a single jsonrpc-remote-cartesi-machine instance. For that we need to be able to keep rolling the state using just cli commands without issues.
Context
Test case:
The final output is:
Notice that we have 3 port listening, where just 1 was expected. If we keep doing advances like this, eventually it will exhaust all available ports on the host (about 65535).
Expected behavior
After every advance,
jsonrpc-remote-cartesi-machine
should keep listening only in one port, instead of multiple ports. Preferably in the same initial port8000
. If it's not the same port, the cli must return the next port the user can connect to, this could be optional and saved to a file, although I dislike this port changing behavior (at least in the cli).Use case
The idea here is to be able to implement a rudimentary "node" using just the cli to perform advance/inspect states to a single
jsonrpc-remote-cartesi-machine
instance. For that we need to be able to keep rolling the state using just cli commands without issues.