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
I've seen this a few times - when I leave Pluto running overnight, and put my computer in hibernate (i think?), the WebSocket communication is broken.
On the client side:
HTTP requests work fine. Opening a new notebook (with new UUID) still works.
The socket is openened, but no messages are received. I can send (bad) messages without closing the socket.
On the server side:
There are no errors in Pluto, not even for bad messages or closing the socket. Last night's sockets closed, and this error was thrown in Pluto.jl:457.
system: Windows 10, pluto running on Julia v1.0 in Legacy WSL Ubuntu 18
The text was updated successfully, but these errors were encountered:
This is the intended behaviour: if the client wasn't alive to process updates, the connection should be closed. (Otherwise the notebook can get out of sync while it is sleeping 😴)
fonsp
removed
the
one day
Closed because we won't work on it soon, will be opened again later.
label
Apr 10, 2020
I've seen this a few times - when I leave Pluto running overnight, and put my computer in hibernate (i think?), the WebSocket communication is broken.
On the client side:
HTTP requests work fine. Opening a new notebook (with new UUID) still works.
The socket is openened, but no messages are received. I can send (bad) messages without closing the socket.
On the server side:
There are no errors in Pluto, not even for bad messages or closing the socket. Last night's sockets closed, and this error was thrown in Pluto.jl:457.
system: Windows 10, pluto running on Julia v1.0 in Legacy WSL Ubuntu 18
The text was updated successfully, but these errors were encountered: