Damir Jelić

The first step would probably be checking out what's going wrong using [mitmproxy](https://github.com/mitmproxy/mitmproxy/).

If you only close the buffer or if you `/part` as well? `/join` works for the latter.

I'm afraid nothing of the sorts is implemented. Reloading the script or restarting Weechat is the only way to get it back, unless someone sends a message in the room.

It just needs to be done, though the exact commands need to be designed, closing the buffer should also leave the room. This script is in maintenance-only mode and further...

While we do use the `Queue` module it isn't part of the project. I can't really answer how you installed `queue.py` there.

The error happens [here](https://github.com/poljar/weechat-matrix/blob/master/main.py#L269). Adding a `print(error) reveals this error message: ``` 21:39 python: stdout/stderr (matrix): The operation did not complete (read) (_ssl.c:1123) ``` I have no idea why that...

There are a couple of closed issues which explain how to mitigate this: https://github.com/poljar/weechat-matrix/issues/27#issuecomment-584323279 https://github.com/poljar/weechat-matrix/issues/69#issuecomment-478168413 https://github.com/poljar/weechat-matrix/issues/123#issuecomment-543573043 https://github.com/poljar/weechat-matrix/issues/195#issuecomment-635544297

There's [this](https://bugs.python.org/issue33090#msg379423) comment on the Python bug tracker pointing in the same direction as well: > tl;dr SSLObject and SSLSocket cannot be safely used by multiple threads at the same...

The the `_socket.py` file seems to come from wee_slack.py, it lists [websocket-client](https://github.com/wee-slack/wee-slack/blob/master/Pipfile#L7) as a dependency which seems to be [this](https://github.com/websocket-client/websocket-client/blob/master/websocket/_socket.py) file. The traceback was reported because there seems to be...

Oh nice, it wasn't my fault doing weird things in the end after all. :sweat_smile: