tired of hacky workarounds to do a 'wait 1 second' in batch scripts so i put an exe in %WINDIR% that just waits one second when called

and now it's just this to wait:

@ECHO OFF

FOR /l %%x IN (1, 1, 3) DO (
  POWERNAP
)

how distracted did I just get? wacom tablet stopped working so I wanted to write a batch script to reboot the service, needed to wait between 'stop' and 'start' commands so I remembered I have VS installed and can compile exe files to easily call from anywhere on the system so. yeah. still haven't restarted the tablet though

note to self: remember that this makes my scripts not work on other pcs

you might have noticed that tuftbot has been offline for a couple days

apparently this is caused by a docker container spawning tens of thousands of threads, which end up defunct and are never actually dealt with. Over the course of a week, this builds up to a level where no new threads can be created; the whole server just grinds to a halt.

What can I do to get rid of those zombie processes once a certain amount has been reached? Can I tell my container to do something like a Java garbage clean once it reaches 20 defunct threads?

The bug has been reported to the dev already, but in the meantime I would like a flex seal type fix just so I don't have to wrangle my way through a barely-responding server every Saturday.

i like this language for the most part but sometimes it's just incomprehensible

rgbcodes = list(zip(*[iter([i/255 for _,v in enumerate(rgbcodes) for i in v])]*3))