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 reloading my client webpages that are using websockets to communicate with a racket websocket server I see error messages such as:
tcp-read: error reading
system error: Connection reset by peer; errno=54
context...:
/Users/endobson/proj/racket/plt/racket/collects/racket/port.rkt:1156:4: try-again
in my terminal output.
These seem to be uncaught exceptions, and they dont seem to be coming from any of my provided code. The server internals should be handling these exceptions and not letting them get to the uncaught-exception-handler, especially since handling a reset tcp connection should not be an error condition for the server.
The text was updated successfully, but these errors were encountered:
When reloading my client webpages that are using websockets to communicate with a racket websocket server I see error messages such as:
in my terminal output.
These seem to be uncaught exceptions, and they dont seem to be coming from any of my provided code. The server internals should be handling these exceptions and not letting them get to the uncaught-exception-handler, especially since handling a reset tcp connection should not be an error condition for the server.
The text was updated successfully, but these errors were encountered: