Ask HN: Did you encounter any leap year bugs today?
11–20 of 498 posts
Re: Ask HN: Did you encounter any leap year bugs today?
#12Re: Ask HN: Did you encounter any leap year bugs today?
#13Re: Ask HN: Did you encounter any leap year bugs today?
#14Can't you just backdate some servers to confirm the fix?
I guess this might be less-trivial if you've got a distributed multi-service architecture and perhaps also depend on APIs that aren't under your control in the first place.
Re: Ask HN: Did you encounter any leap year bugs today?
#15https://www.reuters.com/world/asia-pacific/leap-year-glitch-...
Re: Ask HN: Did you encounter any leap year bugs today?
#16Interestingly, Azure had this bug some years ago too leading to an outage. https://azure.microsoft.com/en-us/blog/summary-of-windows-az...
Re: Ask HN: Did you encounter any leap year bugs today?
#17Re: Ask HN: Did you encounter any leap year bugs today?
#18One cleanup script broke because Python doesn’t have a clean way to subtract a year, and if you do now.replace(year=now.year-1), you get a ValueError when now is 2/29. It’s easy enough to address. There are various StackOverflow posts on such things. Here is one: https://stackoverflow.com/questions/54394327/using-datetime-...