sigh. At $DAYJOB, a user of my code is loading data. Half a million records (~300MB CSV) is taking about 3hr. That works out to ~3k records per minute which is perfectly cromulent for the work being done. Except the network group-policy locks the screen and then logs the user out of the VM after 1hr of inactivity. So they need to babysit the process and jiggle the mouse every so often. Instead of fixing the policy that kills a running process if the user has walked away from the machine, the proposed solution is to include a GUI automation library in my code to jiggle the mouse every so often to fake activity. 😑 (apparently there's a WinAPI SetThreadExecutionState() that lets Windows know that stuff is happening and shouldn't activate the screen-saver or power-savings)