While running run.py using launchd, it will occasionally stop working for long periods of time.
Here's an example from yesterday (recall first entry in comma-separated values are time stamps [seconds since epoch]:)
Note that there's a gap of nearly 30,000 seconds, or roughly 8 hours, before and after the red line, yet these two consecutive logging entries should be no more than around 30 seconds apart. I think it restarted when I restarted the computer for other reasons. This happened before while I wasn't even running Discord, so I don't think that's the cause. None of the logging files really provide an explanation. And the computer was definitely not asleep for 8 consecutive hours: I clearly remember doing quite a bit of work during that time period. I suspect it might be launchd failing.
While running
run.py
usinglaunchd
, it will occasionally stop working for long periods of time.Here's an example from yesterday (recall first entry in comma-separated values are time stamps [seconds since epoch]:) Note that there's a gap of nearly 30,000 seconds, or roughly 8 hours, before and after the red line, yet these two consecutive logging entries should be no more than around 30 seconds apart. I think it restarted when I restarted the computer for other reasons. This happened before while I wasn't even running Discord, so I don't think that's the cause. None of the logging files really provide an explanation. And the computer was definitely not asleep for 8 consecutive hours: I clearly remember doing quite a bit of work during that time period. I suspect it might be
launchd
failing.