201–210 of 498 posts
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 amu…
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.)
Earlier quoted context omitted.
Wired: LLM are practically AGI Tired: ChatGPT thinks February 29th isn't a valid date.
For the record, both ChatGPT-4 and Gemini Ultra affirmed that it's a valid date. Gemini reasoned through it and GPT-4 ran python code to make sure 2024 was divisible by 4.
Earlier quoted context omitted.
A simple fix would be to change it to a multiple of 4 (e.g. 124 years). Then it would fail every 100 years.
2000 was a leap year so it would not fail in 2100. But it would indeed fail in 2200/2300/2400 as 2100/2200/2300 are not leap years.
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…
Wired: LLM are practically AGI Tired: ChatGPT thinks February 29th isn't a valid date.
Earlier quoted context omitted.
Wired: LLM are practically AGI Tired: ChatGPT thinks February 29th isn't a valid date.
For the record, both ChatGPT-4 and Gemini Ultra affirmed that it's a valid date. Gemini reasoned through it and GPT-4 ran python code to make sure 2024 was divisible by 4.
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.