andrewpiroli / nos-mct Goto Github PK

If NUM_THREADS is less than 1 and the force flag is set the program will crash.

The expected behavior is to handle the user error and automatically set NUM_THREADS to a safe value of 10.

Allow multiple device inventories or job files to be passed and combined.

Run with “--threads 26” a message will display about NUM_THREADS out of range and being reset to 10, but 26 threads will still spawn.

The program runs nearly to completion, then when all the subprocesses are done (the final line of run() does execute) it deadlocks in the ProcessPoolExecutor context manager. Spamming Ctrl-C shows it's waiting on the executors shutdown(wait=True), which should return immediately because the subprocesses are done.

Only happens inside the debugger and when the -v option is used.

I'm not sure why this happens, works fine without a debugger, even when stressed with loads beyond what it was designed to handle (30+ processes). Possibly the debugger interfering with one of the QueueProxy's?

I will have to try with different debuggers...