hexchat | IRC client for Windows and UNIX-like operating systems | Chat library

The only other question I can find about terminating Python timer threads is this one: how to terminate a timer thread in python but that only tells me what I already knew from reading the threading documentation.

I am writing a GTK app in Python. It is interfacing with HexChat via d-bus. Because there is no D-bus signal when a user changes context (switches to a different IRC channel or server window) my original design waited until the user interacted with the GUI in some way to see what context we are currently in. The downside to this is entry boxes which need to be switched out can't really be used to switch contexts, because if a user starts typing, the changed signal is issued and the contents get saved to the old context, which is incorrect behaviour.

To solve this, I decided to use a threaded timer task to check what the current context is every 0.5 seconds. The thread function checks the current context, updates a variable in the class, and then re-starts itself with another 0.5 second delay. This works perfectly and is fast enough that it will keep up with users switching channels often.

However, even when I add a TimerThread.cancel to my __del__() function, instead of my program exiting it just hangs until I give a keyboard interrupt. I also tried doing a TimerThread.cancel, sleep(0.1), TimerThread.cancel again just in case I happened to cancel the timer as it was in the context-checking function. Same result. I also tried putting the TimerThread.cancel in the onDestroy function (which will in turn call the __del__ destructor) but no change. The GTK loop exits, and the GUI disappears, but the program just hangs in the console until keyboard interrupt. When I do give a keyboard interrupt, I get a traceback error from the threading library.

Is there some other way to terminate the thread? Is there some other step I need to take to kill the threading library before exiting? Am I misunderstanding how Timer threads work?

Here are the relevant sections of the code: https://paste.ubuntu.com/p/kQVfF78H5R/

EDIT: Here is the traceback, if that helps.

When attempting to connect to a socket configured with SSL and the WebSocket Hook the connection fails.

JavaScript WebSocket Request:

I have a list of dictionaries in python as follows:

I've coded a non-evil, non-spammy IRC bot in PHP, using fsockopen and related functions. It works. However, the problem is that I need to support proxies (preferably SOCKS5, but HTTP is also OK if that is somehow easier, which I doubt). This is not supported by fsockopen.

I've gone through all search results for "PHP fsockopen proxy" and related queries. I know of all the things that don't work, so please don't link to one of them.

The PHP manual page for fsockopen mentions the function stream_socket_client() as

similar but provides a richer set of options, including non-blocking connection and the ability to provide a stream context.

This sounded promising at first, supposedly allowing me to just replace the fsockopen call with stream_socket_client and specify a proxy, maybe via a "stream context"... but it doesn't. Or does it? I'm very confused by the manual.

Please note that it must be a PHP code solution; I cannot pay for "Proxifier" or use any other external software to "wrap around" this.

All the things I've tried seem to always result in me getting a bunch of empty output from the server, and then the socket is forcefully closed. Note that the proxy I'm trying with works when I use HexChat (a normal IRC client), with the same network, so it's not the proxies themselves that are at fault.

I am using the HexChat client on my local machine. I have been using an unregistered nick, eg. foobar. When my connection has dropped I get a message when I try to reconnect:

foobar is already in use. Retrying with foobar01... foobar01 is already in use. Retrying with foobar02...

This has been like this for weeks. My actual username I am trying to use is not something anyone wold be using so it seems it is locked. Obviously I cannot register the nick because I can't connect with it.

What's the solution?