-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZMQ port hardcoded and not editable via the GUI #1774
Comments
The Lines 396 to 412 in 18aad91
Which is called from Line 497 in 18aad91
Which is called from Lines 851 to 853 in 18aad91
It uses the When calling from the CLI, we do already overwrite some parts of the config with the CLI provided options, for example, to enable/disable ZMQ entirely: Lines 1924 to 1928 in 18aad91
Next to this block, we should also support specifying the ZMQ port explicitly and overwriting the appropriate config fields:
|
Another nice option could be to try to automatically detect a free port using We still need to know what the port is in order to pass it to the backend, so just calling this by itself wouldn't work, but we could use it to write a utility function to discover a free port, e.g.: def find_free_port():
ctx = zmq.Context.instance()
socket = ctx.socket()
port = socket.bind_to_random_port("tcp://127.0.0.1")
socket.disconnect()
return port |
[WIP]
As of now we do not have an option to choose the ZMQ ports via the GUI and it has been hardcoded to
tcp://127.0.0.1:9000
for the controller address andtcp://127.0.0.1:9001
for the publish address. Sometimes there is an issue when there are multiple SLEAP applications that are open and trained with, leading to "ZMQError: Address already in use" as mentioned in discussion #1751.In order to solve this, we need to make some changes as listed below:
The text was updated successfully, but these errors were encountered: