<
8000
span class="js-stale-session-flash-signed-in" hidden>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
Yes, this is important because currently a WebSockex process exits silently in case of errors. Also please mention the terminate/2 callback in documentation and examples to highlight the importance of error reporting in terminate/2.
@jurta It shouldn't be completely silent. If there was an error or any other kind of non-normal exit then there would at least be an exit message that was printed. If it was an error in a callback then it should also have a stacktrace associated with it.
If that's not happening, then I would consider it a bug.
Activity
jurta commentedon Jul 18, 2017
Yes, this is important because currently a WebSockex process exits silently in case of errors. Also please mention the
terminate/2callback in documentation and examples to highlight the importance of error reporting interminate/2.Azolo commentedon Jul 18, 2017
@jurta It shouldn't be completely silent. If there was an error or any other kind of non-normal exit then there would at least be an exit message that was printed. If it was an error in a callback then it should also have a stacktrace associated with it.
If that's not happening, then I would consider it a bug.
As for the documentation, PRs are welcome. 😺
khodzha commentedon Sep 9, 2017
not creating new issue, but what's the proper way to disconnect from server?
Azolo commentedon Sep 14, 2017
I think that is a really good documentation issue. But the proper way is to send a
closemessage.The easiest way to do this is probably with a
:closecallback return from a cast.