Dunno why people would blame the Celery devs for that bug - if you're setting the clock on production servers to a non-monotonic TZ you are going to have a bad time.
So you basically blame people for living in countries that use daylight saving
time? O_O
Also, I would understand if it were tasks between 2AM and 3AM that run twice
in transition from summer time to winter time (there are two 2:30 that day,
after all), but the bug affected tasks scheduled for the middle of the day.
I mean, Celery is a pretty amazing library. It has flaws, but I doubt this new project has no flaws. They are just unknown still.
For that specific bug in question, does KQ have logic around DST switch? I was not able to find any. So it looks like you would have the same bug in KQ, right?