CException | Lightweight exception implementation for C | File Utils library

Can I render an openCV animation from a background thread in Python?

Here is my attempt:

I am getting confused here. According to my Windows 10 Regional Settings the Long Date format is:

I was adjusting some MFC code:

I'm currently running a FileZilla FTP server on a network. My issue is that on seemingly random machines, when the user navigates to a directory (which they are able to do) and attempts to ls (i.e. data transfer) their end hangs waiting for a response, while the server reports this 425: Can't open data connection for transfer mentioned above. This result varies depending on the client machine used, where some (either local or remote) are able to proceed and others stuck here. I understand that this is because simple FTP commands like CWDing operate on the 20/21 ports, whereas FTP data transfer operate on some other port number, which in turn may be blocked by a firewall somewhere along the chain. My question is, how do I account for these varying ports (if this truly is the issue), as as best I know they could be anything above 1024?

My end goal with this project is to implement a very simple FTP solution, ideally using WinINet, however, so far I've run into the same problem:

I see at catch exception by pointer in C++ , it is said to throw an exception by value and catch it by reference.

Therefore, I write the following codes:

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.

TL; DR

This was indeed a bug in Motor 1.2.0 that was promptly fixed by A. Jesse Jiryu Davis and is available in version 1.2.1 or greater of the driver.

Original Question

I wrote a program to monitor changes to a MongoDB collection using its new Change Stream feature, on Python 3. Here's the MCVE:

I am trying to create a function that takes a variable number of matrix in parameters and multiply theses to a first one. I can read a first one using va_arg, but the next call of va_arg will cause an access violation.

Here is how i declare my method :

MFC defines functions to throw predefined exceptions. For example, you use ::AfxThrowFileException() to throw an exception of type CFileException. But what if I define my own exception class, which derives from CException? What is the preferred way to throw it?

Are there problems if I simply do this:

I just want to make sure that i understood the reference correctly.

I got a class A that contains that sets the unique pointer within it's constructor