bubbleboy14

Results 53 comments of bubbleboy14

Hey @GooVincent, a few notes: 1) only call rel.dispatch() once (in your example, main()) looks like the correct place) 2) no need to call rel.signal() - websocket-client takes care of...

I tested your client code against my usual websocket server, @GooVincent, and didn't notice any problem with reconnects - every time I turn the server off and on, the client...

@GooVincent I tried your server example, and _finally_ see what you mean - this is about reuse of the WebSocketApp instance after the server closes the connection. Hah, I should...

I think I encountered this as well! This was happening because WrappedDispatcher (via reconnect() and timeout()) wasn't passing reconnecting=True to setSock(). I think this was actually probably my oversight, oops,...

Hey @hk8805 try it without the "rel.signal" line - that's already being taken care of here: https://github.com/websocket-client/websocket-client/blob/69e470fee083cd4d5f42bccaff3a6168bfeee863/websocket/_app.py#L142 Anyway, give that a shot and LMK how it goes!

Hello again @hk8805! I just reproduced this in a Windows 10 virtualbox, and fixed it in a new rel release, [0.4.9.3](https://pypi.org/project/rel/). So upgrade to the latest rel: ` pip install...

Yes that's right - you can remove the "rel.signal" line from your code (as that is already accounted for by websocket-client). And also please update rel to the latest version...

@devanshubisht rel can be used instead of threads to run multiple WebSocketApp instances. I wasn't able to reproduce your issue - calling ws.close() inside the on_message() callback works fine on...

@devanshubisht interesting. As a test, could you put this line near the top of your code: ``` rel.initialize(["poll", "select"]) ``` On FreeBSD, kqueue seems to work fine. However, I guess...

Thanks for the bug report @waza-ari , much appreciated. The problem appears to be with rel's usage of kqueue. Would you be willing to help me debug this issue? Here's...