so the app at dayjob has an internal scheduler, one of the formats for which handles, like, "on the 12th at 8am" tests for it were failing intermittently, in daily CI job only i'm curious if there are any devs out there whose trauma runs deep enough they already know the story
-
-
which is to say, this feature is *architecturally* broken by a 5-dimensional corner case that a sufficiently thorough test suite will catch in our case, it showed up because the CI job was run at 6 AM, which the UTC to Eastern offset from server to application converted to 2 AM
Show this thread -
oh, for a little extra cherry on top can you guess how many cases of this specific type of schedule being used exist in the app, outside of the test suite go on i bet you can guess if you try
Show this thread
End of conversation
New conversation -
-
-
Because at 2am, Daylight Saving kicks in and they just fucking skip the whole hour. Expected behavior? Disallow selection of non-existent times? Or shift the selected time forward by an hour?
-
it'd basically work fine if the "should i run" check checked >= instead of == it records when it actually last ran the thing so it's not gonna run it too many times or anything would incidentally make the system more resilient to outages
- 1 more reply
New conversation -
-
-
what
-
daylight savings cutover, it's at 2 AM, i guess to make it less impactful. clock jumps from 1:59 to 3:00
- 1 more reply
New conversation -
-
-
god i hate time so much
-
can there possibly be anything worse? only time will tell
End of conversation
New conversation -
-
-
Twitter spoiled this for me by showing the dirty stuff up-front, but I have indeed debugged more than one variant of this problem in real life. (Also “this event happens at a roughly constant rate but once a year it spikes to double the hourly throughout and sets off alarms.”)
-
*puffs chest* I was already being traumatised by this shit in 2012 man *unpuffs, sobs* http://www.logophile.org/blog/2012/09/30/troubles-with-timezones …
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.