4 ms·
Today, February 29th, is a "leap day" which happens every 4 years in a "leap year"... Otherwise, the last day of February is the 28th, and today would normally
by powertower 15y ago
Today, February 29th, is a "leap day" which happens every 4 years in a "leap year"... Otherwise, the last day of February is the 28th, and today would normally be March 1st.
I'm assuming that when the day rolled over, it caused an issue with an internal system at Microsoft, that had something to do with certificate dates and/or timestamps.
It's not just Microsoft that it's happening to, today I could not automatically renew any domains at Namecheap that expire tomorrow because the registry could not produce the correct expire-at date.
Leap days cause odd issues.
- DrJokepu 15y agoHow the hell is that possible? Every platform out there has high quality date libraries. It's a cliché that date & time operations are very complicated (leap years, leap seconds, time zones, daylight saving time and so on), every even marginally competent developer knows instinctly to stay away from writing their own date & time code and trust a library instead to do the heavy lifting. In addition, every tester should know that when dates are involved, they should try Feb 29th and see if it breaks anything. How can bugs like this slip through?
- crcastle 15y agoAlso whether or not a year is a leap year is easy to calculate: Year divisible by 4? => leap year; year also divisible by 100? => not a leap year unless year also divisible by 400