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
{{ message }}
This repository has been archived by the owner on Mar 3, 2020. It is now read-only.
After calling app.stop(), the (web)socket is left open, according to netstat. Doing app.run() after stop() opens a new socket, but the old one is left open.
Is this intended behaviour?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After calling
app.stop()
, the (web)socket is left open, according tonetstat
. Doingapp.run()
afterstop()
opens a new socket, but the old one is left open.Is this intended behaviour?
The text was updated successfully, but these errors were encountered: