List of 2020 Leap Day Bugs

[AppDefects]

The following is a list of many bugs caught on or near leap day, February 29, 2020:

• Some people reported probable leap year bugs with their Amazon purchase experiences.  Reports: 1, 2
• Many people reported their cell phones were showing Feb 28th when it was actually Feb 29th, or some variation of showing the wrong date.  Most appear to be on the Sprint network, and for at least one, Sprint confirmed the issue and stated they were working on it.  Reports: 1, 2, 3, 4, 5
• AppDaemon open source home automation software crashed on leap day due to trying to create a date of 3000-02-29.  (The year 3000 is not a leap year.)  More details in the related GitHub issue.
• A person reported a possible bug with Patreon
• A person reported that all the key cards and elevator in their hotel stopped working because of the leap year.
• Many developers mentioned that they encountered leap year bugs in their own code.  Thanks for sharing!   1, 2, 3, 4, 5, 6, 7, 8

More examples of leap year bugs can be found on StackOverflow,

[Caute_cautim]

This is quite interesting, no wonder applications and programmers fail:

The Leap Day alone overcorrects the calendar, requiring we remove a Leap Day every century year. But that under-corrects the calendar, requiring we put a Leap Day back in, every four centuries. Behold the Gregorian Calendar.

Regards

Caute_cautim

[AppDefects]

Any takers on switching to the Hanke-Henry Permanent Calendar?

[Caute_cautim]

@AppDefects   Would the world accept uniformity and consistency?  Think of the issues associated with this?

Regardss

Caute_cautim