Did you encounter any leap year bugs today?
After a frantic scramble this morning, our billing team has finished patching a bug which erroneously was charging our monthly subscribers for an extra day.
All test suites are passing now, and SRE has scheduled a postmortem after the QA confirms the fix in 2028.
Heard from a friend in China: the age calculation portion of the app to schedule a marriage certificate had a bug where they subtracted 22 (legal minimum age) from the year, which resulted in 2002-02-29 which doesn't exist. The app intends to compare this against the user's birth date. The error handling code assumes all errors are from the comparison. The app then rejected all marriage certificate appointments by complaining that the users are too young to marry legally.
No, but some of our software writes data to rotating directories named after the date, and while doing some manual debugging on a test system, it started failing to create these directories the first time it rotated on Feb 29 UTC. Turns out it just happened to run out of disk space at that time, but I had myself convinced that it was a leap year bug for over an hour. :)
I have a friend who was born on Feb 29, and in Quebec your driver's license fees must be paid on or before your birthday or your license is effectively revoked (It's a convenient reminder). He was on his way to pay them on the 29th and got pulled over for having an expired license... after some awkward common confusion with the police they came to the conclusion that the license bureau moves your "reminder" birthday up by 1 day when the actual day is on Feb 29, instead of back to March 1st, so they don't miss out on 3 years of license payments for leap year birthday citizens.
The cop had never encountered this before (1/1460 chance of occurring * the odds of being pulled over on that day)
I don't think they ever patched this, so watch out if you're a leap day license fee procrastinator in Quebec!
We have a product that uses ChatGPT via the API, using the 3.5 turbo version. Our query involves some dates. Instead of giving back text like it usually does, today it has been giving errors because it does not think 2024-02-29 is a valid date.
This is easy to reproduce with the web interface, at least sometimes [0]. It start out by saying it's not a valid date and then as it's explaining why it isn't it realizes its mistake and sometimes corrects itself.
[0] https://chat.openai.com/share/37490c9f-81d6-499f-b491-116536...
Yes.
> During the morning on Thursday, no ICA store in Sweden could accept card payments. Instead, you had to use cash, Swish or pay via their app.
> The reason behind the problem was an internal problem in the payment systems at ICA as a result of an extra day in February, leap day.
ICA being the biggest grocery store chain in Sweden
The other way around! Today a few services that don't congratulate me on my birthday (on non-leap years) did. I was born on February 29th.
This one is rather specific, but a game rhythm based Final Fantasy game called Theatrhythm Final Bar Line is simply not allowing people to play today because it has an internal system that awards prizes for specific days and they didn't handle the case of what to do when it's on a leap day. You can boot it up but can't actually play the game as a result.
Not working on the game or anything but found it moderately amusing as someone who owns the game!
Yes, I have a bot that posts daily San Francisco weather records to Mastodon. It did not post as scheduled today. This is because I am looking at all the high temperatures, low temperatures, and precipitation on today's date from 1875 (about as far back as there are digitized weather records I can work with) to the present. Since there was no such date as February 29, 1875 it is throwing an error.
One thing I have learned from HN is that datetime issues are hard, prolific, programming language agnostic, and not to trust myself to get the logic right. (The same applies to floats.)
Surprised no one else mentioned the Cloudflare billing issue today. I got incorrectly invoiced yesterday and the file was named cloudflare-invoice-1970-01-01.
https://www.cloudflarestatus.com/
I know I'm late to the party, but I have a Python script that creates a security.txt for one of my own project, and it sets the "Expires" date to one year in the future.
Old code:
expires = datetime.datetime.now(tz)
expires = expires.replace(year=expires.year + 1)
It broke yesterday, throws an exception ("ValueError: day is out of range for month"). It's kinda obvious that it does.
Fixed version code:
expires = datetime.datetime.now(tz) + datetime.timedelta(days=365)
expires = expires.isoformat(timespec="seconds")
Now we're just going 365 days into the future. Of course, this has a slightly different meaning and outcome, we are not always ending up on the "same date next year". But in this use case it doesn't really matter.
Didn't see it mentioned here but cloudflare sent me an invoice today and the attached PDF was titled cloudflare-invoice-1970-01-01.pdf :)
It's scary how much code out there is less than 4 years old, and even scarier how much of it is because someone decided to somehow rewrite it unnecessarily and thus introduce this bug. I don't even want to know how many people think the code they wrote will be in use for more than 4 years.
I can understand getting the years 2000 (leap), 2100 (not leap), 2200 (not leap), and 2300 (not leap) wrong. But getting the year 2024 wrong is, disappointing, to put it diplomatically.
Not today but several years ago while lending a hand on a project that was wildly overdue and the guys needed all the help they could get. Disclosure: it was not in software that was in production yet(otherwise you would have likely heard and been affected by it by now I suspect). The software's purpose was dealing with commercial airlines - routes, connections and all that. The travelling salesman problem basically. The software was meant to replace an antique system which no one knew how to maintain since in 2020 it was still running on mainframes and written in fortran. There were specifications on how the system worked but there was no one who could even read the code. Anyhow, the way dates were stored, read and calculated was absolutely insane. I can't recall what the exact deal was, but each date was represented with either 4 or 5 bytes with some really awkward algorithm to make it into something meaningful. With a bunch of additional patches surrounding Y2K.
Unfortunately it was a lot more subtle than getting March 1-st instead of Feb 29-th. Each date was calculated with a dynamic offset depending on the month and year. So during leap years, everything was fine until the 14-th of May at 01:00 UTC. The second the clock hit, 14-th of May at 01:01, all hell broke loose incrementally as time want on until the end of each year. The weird string representation for Nov 1-st was being calculated as January 3-rd for instance. But as soon as the clock hit January 1-st, everything went back to normal. It took 6 people 2 days to figure it out. As you might expect, this was not mentioned anywhere in the documentation.
I'm not sure what has happened ever since, but if the system made it into production and you didn't get stuck in an airport... You're welcome lol
The Casio F-91W doesn’t account for the year, it showed today’s date as Thursday, March 1st.
Remember, always use a library for cryptography, payments, and date calculations.
We have a rails 6 app, and there's a test that essentially expects time_ago_in_words(1.year.from_now) to return "about 1 year" (as part of a user facing message). The test failed. I thought it's a flaky test but i was able to reproduce it locally. Turns out executing that code on a leap day returns "almost 1 year" instead.
Can test it in rails console if you are interested:
irb(main):001:0> include ActionView::Helpers::DateHelper
=> Object
irb(main):002:0> distance_of_time_in_words(Date.new(2025, 2, 28), Date.new(2024, 2, 29))
=> "almost 1 year"
irb(main):003:0> distance_of_time_in_words(Date.new(2025, 3, 1), Date.new(2024, 2, 29))
=> "about 1 year"
irb(main):004:0> distance_of_time_in_words(Date.new(2025, 2, 28), Date.new(2024, 2, 28))
=> "about 1 year"
Why this is not a global holiday? Let's all come together and agree to do nothing on this bonus day. Calendar Problems solved.
My sister is staying in a hotel and all the keycards stopped working.
I certainly did. There is a batch process to cull old records. It checks for customers who do not have a date of death recorded but are > 130 years old, as it assumes that we weren't informed of their death.
It takes 130 years from the current date and uses that in an SQL statement to compares it to the date of birth. DB2 doesn't like 1894-02-29.
Apparently it happens every 4 years, but no-one can be bothered to fix it.
Unless you're in your 70's, YouTube doesn't allow you to buy premium if you were born on a leap year, because their age calculation is broken, and it thinks you're under 18. Google One works fine. Support will suggest that you change the birthday on your Google account, which breaks account recovery processes that depend on you furnishing matching identity documentation. Mind-boggling.
Because nobody at YouTube has apparently ever encountered this problem, I ended up having my partner buy a family plan. As much as I hate paying so much a month for YouTube of all things, screen-off background play is a paid feature on iPhone, having one of the two accounts on your TV showing ads is absolutely infuriating and I'm not sure I fancy risking an account ban for anything they can associate with someone costing them ad revenue.
My monthly bus passes for both February and March did not work in Dallas today. The driver was aware of the issue and just waved me in.
Our Sophos anti-virus at work blocked access to every website this morning because of the leap year, had to disable the web filtering to get us back up and running.
Python.
cls = , data_string = 'Feb 29 04:55:03.687' format = '%b %d %H:%M:%S.%f'
E ValueError: day is out of range for month
Yes, an amusing one: the Android app for the Berlin public transport, on the 29th, listed the results with the date of the previous day (28th).
The funny thing is that the list is prefaced by a banner saying that this is a known bug, and the results actually refer to the 29th.
Interesting way to workaround a bug :)
Spotify Artist which is app for managing as name states your artist profile should allow you to run promo campaigns but they need to be set till the end of the previous month. Well. 29 February according to spotify is not a valid February date.
I know it's somehow an edge case but it's one which appears every four years so I dont understand how it could be missed by such a big company.
Python script using datetime crashed with a "ValueError: day is out of range for month" exception.
We got a bunch of close-dated yogurt the other day.
Several were best by 2-27, 2-28, 3-01, and 3-02, but none by 2-29.
One of the largest food store chains in Sweden had their entire card payment go down because someone forgot to handle leap years!
One 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-...
Yes, in T-Mobile billing, I tried to set up automatic payments on the 26th, but the system both told me that this was impossible (because it was "less than 2 days from the end of the month") and then accepted it, because why wouldn't it.
Yes - I triple-checked the calendar to verify my suspicion this February might have 29 days. The result was always negative - it seemed 28. Then February the 29th actually came. A bug apparently occurred in my mind.
Found one on iMessage! Wished former coworker a happy birthday, and it said, "Siri found a birthday: March 1". Though when I pressed update, it correctly marked it as the 29th.
Many years ago I visited Laos. We crossed the border at a rather remote and little-used border crossing.
Laos issues 30-day tourist visas on arrival. We arrived on February first and I have a Laotian visa valid until February 30th, 2011.
Not a leap year bug but a February bug. Ended up being inconsequential, but still makes for a fun story.
Last night around 8:00 PM I noticed the time on my Linux laptop was wrong. I tried to reset it manually and got a "Cannot set current time" error. Closed the dialog and a minute or two later the time reset to the correct value. I shrugged it off as something random.
Then today I get home from work, un-suspend that same laptop and the time and date are both wrong now. It has it as around 10pm last night. Turn off auto updates and turn that back on, and nothing happens. Wait 4 or 5 minutes, nothing happens. So I finally decided to reboot, which does indeed clear things up. Only then did I remember that today is Feb 29th and make the connection that this might be related to the leap year.
Can't say for 100% certain that it was, but it would be one hell of a coincidence otherwise.
Stupid question. How do these bugs happen?
If you just take the naive approach and calculate everything as unix timestamp deltas, “yesterday” in human terms will still be 86400 seconds ago. No difference leap day or not.
If you use a date library with fancy “subtract one day” functions, it should also be handled automatically. Just like you don’t have to care that March has 31 days and April 30? No difference if leap day or not.
Someone must have spent a lot of effort to manually create date logic, hard coding the number of days in a month or something?
Only other edge case is if someone takes a 2024-02-29 timestamp and modify the year part, without using date library to do so. That should be rare, only use case is a yearly report. That’s not something that should take down the whole billing system.
Gusto paycheck didn't come in until a lot later than usual... thought this might have been my last day on the job for a little bit, didn't help that my manager and I's one on one was my first meeting of the day heh.
My Casio F-91W thought it was March the first and got me confused for a moment. But other than that I saw no other bugs.
I wear Xiaomi's Amazfit Pro 3R. Digital. Wrist band. Hung at midnight of 29th Feb today. Did a bunch of factory reset but didn't recover. And then recovered at the morning of 1st of March.
Date is relatively simple.
days_in_month(year, month) :
if(month==2) return days_in_feb(year)
//all other months have constant number of days, always.
days_in_feb(year,month) :
if(!(year % 400)) return 29;
if(!(year % 100)) return 28;
if(!(year % 4)) return 29;
return 28;
And you are done for all Gregorian years.
Payroll software at work had a one-off planned maintenance day today, presumably to avoid worrying about any bugs.
I did.
Unit tests were broken in the CI pipeline because of a leap year. The problem was validating the number of days in a year, but dismissing a leap year. The code assumed the number of days in a year was 365.
Yeah! Our friends got married yesterday, and now they have until 2028.02.29 to legally change their names.
I had to renew my vehicle registration this month. You usually have until the last day of the month to get it done. But this year the state of North Carolina said that was the 28th, not the 29th.
I just checked and realized I have zero annual Stripe renewals that have come through so far today. Not a big surprise, since most of our customers are on monthly subscriptions.
I have wondered about how Stripe handles months with differing numbers of days (for monthly subs), and leap years (for annual subs). Do they accelerate renewals in short months, so that February 28 has all the renewals that normally happen on the 29th-31st of other months? Or do they happen on March 1?
A coworking space I signed a contract for starting on March 1st sent me an email on 02-28 telling me my membership starts tomorrow and welcome on board.
I am gald that in excel, deleting a day from March 1st automatically gives Feb 29 or 28 depending on the year in formula. Before that, I struggled a lot to find last day of month by tracking if its a leap year or not, and keeping an array of months & number of days. Now I simply add 1 to month, and from resulting daye I subtract 1 day. The Date value of that gives me 31 or 30 or 29 or 28.
One of our reporting systems closed month end reporting yesterday. Made everyone mad until they realized things can still be changed today.
Today is the start of the new tax year here in South Africa and my brother wanted to draw the last years worth of transactions from a local financial institution to be able declare his tax.
Setting the date range from 2023-03-01 to 2024-02-29 was not permitted as it says the date range must be within 12 months. Of course a general limit of 12 months is a bit of a WTF too.
I have a small hobby project that scrapes concerts on various venues websites.
Many of the websites don't write out which the year the concert takes place, so in python I will:
try the current year and see if the date has already passed, and in that case I try the next year.
Of course feb 29th is an issue in this case, so some of my scrapers modules crashed.
Using Google Gemini:
Prompt:
> Is 1200-02-29 a valid date?
Answer:
> Python
>import datetime
>
>try:
> datetime.datetime(year=1200, month=2, day=29)
> print("Valid date")
>except ValueError:
> print("Invalid date")
>
>Output:
>
>Valid date
>
>Yes, 1200-02-29 is a valid date.
>
>According to the Gregorian calendar, leap years occur every four years except for years that are divisible by 100 but not divisible by 400. The year 1200 is divisible by 400, and therefore it is a leap year and February 29th exists in that year.
Wrong: the Gregorian calendar didn't yet exist in year 1200, so its rules don't apply for that year.
Now that you mention it, the payment system was not working in a ski resort restaurant in Switzerland this noon.
They had to switch to cash.
The national law enforcement background check portal was down today, I wonder if the leap day had anything to do with it.
My Casio F91W I assumed would know that year YYYY is leap, and would show 29th as Date. No, it showed 1 as in March (it doesn't show months). I had to manually set it back to 28th so that tomorrow it shows correct date.
To be fair, it doesn't ask for year anywhere in settings. It simply doesn't know what year it is.
Had a pair of tests break CI.
At least one of them was the test, code it was testing did its job fine but test could not cope with February 29th. Obviously the test is broken in two different ways: it fails on Feb 29 and more importantly tests the behaviour on $current-date so only tests edge cases on the day of.
Other I didn’t follow.
Yes, a few mildly bad things go wrong on a feb 29th. Everything that handles stuff a year from now for example. Pretty bad for a planning program. But our customers noticed and avoided that. Codebase is too ancient and brittle to even attempt to fix. Or at least boss doesn't want to invest time in it.
I had a unit tests for a Java LocalDate that was being increased by one year. It checked whether the month and day were the same, and failed because the current day (29) didn't equal the year-hence one (28). I changed it to check that the difference between the days was less than two.
Our ETL process is heavily monitored so we never miss a days data, but we got a surprising error "cant build aggregates - missing data, aborting MV refresh, data will be a day old".
It was the year to date (YTD) calculation - no data for 29/2/2023 to compare to today.
My suite failed this morning on an obscure test of a function that converts between ages and dates of birth. Took me ten minutes of head scratching before I realised it was Feb 29th.
’’’
+ if time.Now().Month() == time.February && time.Now().Day() == 29 {
+ t.SkipNow()
+ }
’’’
Fixed.
We had a bug on the 1st of this month. Some billing code liked to invoice on the last day of the month and failed to account for this month having an extra day. Interesting it happened as soon as the "leap month" started. Easily fixed though.
A fiber cable was cut so we had no internet for the morning, probably not leap year related.
Breaking News: The legendary report from 2017 finally cracked yesterday:
queryset.filter(user__last_login__gte=today.replace(year=today.year - 1)).count()
Meanwhile, in the betting world, someone actually placed a bet on the day of the week for February 29, 2020.
Uniting time zones in Kazakhstan today looks like more of a headache, at least to me.
Yup, all our rolling-year calculations failed because you can't have 29 Feb 2023!
Ran into a bug where some code was taking an hour long interval and subtracting 1 year from the start and end times. But the time library handled subtracting a year from Feb 29 as converting it to Feb 28th of the previous year, at the same time. So on-call got alerted because a job failed when an exception was thrown because the start time was after the end time. Fortunately, other than the alert, there wasn't any negative impact. Although, I think if this isn't addressed it may cause issues next year when it includes a bigger interval of time than expected on March 1st.
We had test failing that had to be skipped and worked out in the background.
My (cheap, digital) watch thought it was 1st of March.
Funnily enough when I went to change the date the watch allowed me to select Feb 29th. I wondered if it had supports for leap year and it was off by exactly one year but that's unlikely as it didn't seem like cycling through the dates changed it to 29. Most likely it allows selecting manually the 29th but then skips from 28th to 1st of March every year.
All my billing / calendar booking is outsourced to Paddle / Stripe / third parties so no other issues in my products!
My wife’s company had an issue with this today. A couple hours before I read this she mentioned it to me and I just assumed human error was the cause. Then I read this and it clicked. Crazy shit.
Microsoft is off by one this year, with their 365 line of products
The mcdonalds order waiting thing malfunctioned, displayed de52hg04 instead of 088 and I had to wait a lot longer for my order since it flew under the radar for a while until I spoke to them :)
My daily crontab at just after midnight UTC did not run yesterday. I wrote it off as a server hiccup, but now you got me thinking it might be related to leap years…
Can't you just backdate some servers to confirm the fix?
I work in scheduling software and had no issues today surprisingly. But we have hundreds of end to end tests that cover daylight savings as well as leap years.
Saw my bank book every auto-transfers, like utilities, rents etc.. booked for 28th to be again booked on 29th, i.e. twins appeared. But then those disappeared after the mid-day. Not sure if those were caught and fixed by anti-fraud system as double-charging or was just strange bugs somewhere, but happy that they disappeared, as it would be weird to explain to my landlord about why I decided to pay double rent.
Kind of... Spent a while debugging an issue where the client was convinced he could not schedule new appointments in the system on the 29th.
It turned out he had set another setting incorrectly which was causing the appointment never to be valid.
But the rarity of the date let me wonder in the wrong direction for a while...
Years ago i ran a script to fill a db table with entries for each day by incrementing a timestamp by 86400. It skipped the 29th of this year
“Anyone who thinks programming dates and times is easy probably hasn’t done much of it.” - Peter van der Linden, Expert C Programming
Why are there so many stories about leap year bugs?
I was doing an online check in with the national Argentinian airline. My wife’s and I data was already in the system from the previous checkin. When we were about to confirm we noticed that both of our birthdates where off by one day earlier. I can’t confirm it was related to the leap year but I also cant find another explanation.
I had a few [datetime].replace(year=[current year]+n) in python where n is not divisble by 4 e.g. 2,10
This is in code we use for scheduling
Just AFTER reading about Casio watches in this thread I looked at mine. Sure it displays the date as March 1.
Maybe? My paycheck direct deposit didn't show up until almost 7am. Normally it hits right at midnight.
Yeah, I have a Python script for personal use, and briefly could not figure out why it was crashing. The reason : I was using
class datetime.date(year, month, day)
which was attempting to generate "today, one year ago" by reusing the current month and day, but replacing the year with year-1.
Colombia's largest airline (Avianca) printed today's tickets with the 1st of March as a date
One of the most common QA test cases when it comes to testing date and time sensitive applications.
I have an old client who called and is having issues with their registration/calendar system.
When the page loads it looks for events two years in the future, which as you might guess based on the context of this thread, simply increments the current date's year by two.
Yes. We had some test failures. Test setup was to create records for today, yesterday, last week and last year and make sure they are generated correctly. Well last year's date didn't match today's. Easy fix but it was hilarious.
My new pixel 8 needed an update on the 28th. It told me the update would happen at 2am on the 1st March and duly waited an extra day to perform it. I'm assuming standard Android update policy is not now to wait an extra day.
Yes. Be mindful about if your industrial firmware really needs to know the datetime..
Yesterday in New Zealand (29 Feb) couldn't fill up my car at two petrol stations - both had self-service terminals that were down because of leap year. Ended up having to go inside at a station at pay the old fashioned way.
I have a daily reminder set up in Apple’s Reminders app and it didn’t trigger today.
I'd suggest not waiting 4 years to publish a postmortem, if you're serious
Using Google docs it usually autofills the date for me but today it couldn’t as I typed the date the calendar widget came up. No Feb 29!
I typed 2024-02- waited and it didn’t show up. 2024- then autofilled 2024-03-01
my m1 macbook air, which has been powered down for a few months, would not automatically get the date from the time server, which broke some stuff.
set it manually, no problems, hopefully will be able to turn it back on tomorrow
Hi!
In my internet banking, I needed to schedule one invoice for the last working day of march, 28th, Friday.
System responded that this is Sunday so invoice could not be scheduled.
I don't know if it was a Leap year bug but after midnight my wife's phone still said Feb 29th even though it should have switched over to March 30th at 00:01
I unsubscribed from Netflix and was supposed to have it till the end of februar. But yesterday the 29. there was already no more access ..
Quite trivial, but still a bit ridiculous.
> and SRE has scheduled a postmortem after the QA confirms the fix in 2028.
:)
Not a single one, either in the code at work or anywhere else.
I did, actually!
A couple date form fields on AWS had their date incorrectly set to 2024/02/28 instead of 2024/02/29. Not mission critical, but it is something :D.
I bought a couple guardian bikes a couple days ago. Their website said they would arrive today, February 1. I assumed it was some kind of weird leap day issue.
Do what George Washington and Abraham Lincoln did and just latch to a nearby Monday. That's an instant three day weekend.
Our credit card invoice system shifted all invoices that were due 28th to the 29th of February. Still trying to figure out what happened.
My "smart"watch froze at 23:59 28th Feb
Hikvision access control camera would not let anyone into the building on Feb 29. Had to get tech out to upgrade
My desktop machine did not time out overnight last night and require me to enter my password to resume wasting time this morning.
The calendar lockscreen widget on iOS reported an event that had already happened as upcoming on March 1st, pretty minor
Pandas CI broke today because of the leap day and testing for datetimes. Pretty similar story to the other Python examples.
We did but I only learned of it today! Completely broke a lot of systems until they set the day to March 1st and back
Yes, the local transport Timetables App was showing the 29.02 routes as 28.02 and they have put advice on this problem
Reading the comments here and can't believe that so much software still has these bugs. 2038 is going to be FUN.
Citi Bank's credit card "Merchant Offers" showed some offers as expiring in "-1 days".
My bank sure encountered a bug: they're APIs are returning march 30th for some records.
Unit tests failing because of scenario that offset a date by a number not divisible by 4 and compared...
My Citizen ana-digi-temp from 1985 works perfectly fine and shows Feb 29.... though it thinks it is 1996!
Sunsynk inverter seemed stuck on Feb 29 today 2 March, not sure if leap day or other cause
Found some bugs in TESTS which have been running fine for <=4 years, but failed today.
On AWS Cost and usage control panel:
> Forecasted month end costs
> There isn't enough historical data to forecast your spend
Pretty much all of the self service gas station terminals in New Zealand went down for the 29th
Hikvision access control camera would not let anyone in the building on Feb 29
Just realized. I'm absolutely flabbergasted nothing happened at my company.
I got an invalid grant - bad request from google oauth on one of 3 identical servers
EA Sports WRC.
Crashes on launch. Put the system clock forward and it works... it boggles the mind.
Llama2 models refused to acknowledge that the date was a valid date.
Yes, we had a test fail when generating `12 days ago` strings from a past date.
gpt-4-0125-preview was the output from "date" and commented that my date implementation must be broken because 2024 is not a leap year and therefore the 29th isn't a valid date... Go figure.
According to the Intranet, it was everybody's birthday yesterday.
Didn't even realize it was a leap day until I saw this post.
Fortunately no, we use Carbon in PHP and it is super solid.
My university login website now does not allow me to login
A charge from something I bought today says March 1st.
> after the QA confirms the fix in 2028.
Dang, your QA team is fast.
my home assistant integration for solar/energy monitoring did not register any data for feb 29. from midnight to midnight
Yeah, the AirBnB where I'm currently started renovating the apartment upstairs. I guess that's a bug. In the ideal life, that wouldn't have happened hahaha! :)
shopifies calendars and some ad dashboards are showing 2 days in view instead of 1 for today/yesterday
A few unit tests broke, nothing major.
I got paid early. Is that a bug?
probably teams had one, today it was showing me all meetings from yesterday
Uber is down in Mexico City