rr.serve
should be rr.serve_websocket
, rr.connect
should be rr.connect_tcp
#7766
Labels
😤 annoying
Something in the UI / SDK is annoying to use
🪳 bug
Something isn't working
📖 documentation
Improvements or additions to documentation
🏎️ Quick Issue
Can be fixed in a few hours or less
user-request
This is a pressing issue for one of our users
And similarly,
rerun --serve
should bererun --serve-websocket
(or something along these lines, you get the idea).Users get understandably confused by this. They expect a serving process (
rr.serve()
) to be ready to accept connections from other processes (rr.connect()
), except the two things are in reality completely unrelated: one is hosting a websocket server to be polled by the web-viewer, while the other is trying to connect to the TCP sdk comms pipeline.See e.g. this thread: https://discord.com/channels/1062300748202921994/1295914647165210634
The text was updated successfully, but these errors were encountered: