Olivier Macchioni

Hello @machack666 I have tested the SQL, it works on 9.4.24 and 10.10. So it probably works for all versions between those. As 9.3 is not supported any more since...

Because the job may already be running, and don't want 2 instances of the job running in parallel. I want to re-use apscheduler's `max_instances` limitation mechanism, not re-implement it.

Sorry, I was not clear. The event is not generated within the job, it's generated in an asynchronous process. So we have 2 things: (1) Asynchronous process generating an event...

Possibly - but won't this potentially conflict with a run of the same job which would have be triggered by the scheduler ? The risk I see is the following...

My understanding was that `max_instances` limits the number of instances for a given job in case it takes longer to run than its frequency - cf https://apscheduler.readthedocs.io/en/3.x/userguide.html#limiting-the-number-of-concurrently-executing-instances-of-a-job This code shows...

Thank you for your answer and the time you've spent to understand my issue, and I hope it gives you interesting information on how people are using / abusing of...

To be noted that the change on the DNS server has been reverted until the 7th of January... https://developers.eveonline.com/blog/article/removal-of-redirect-from-.tech.ccp.is-on-jan-7th

I have the same issue... ``` clang -v Apple clang version 15.0.0 (clang-1500.3.9.4) Target: arm64-apple-darwin23.4.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin ```