Earlier quoted context omitted.
> No, 2024 is not a leap year. Leap years are years divisible by 4, except for years that are divisible by 100 unless they are also divisible by 400. Therefore, the next leap year will be 2024.
As the proud new owner of a leap day baby, I find this to be extra hilarious
Ask HN: Did you encounter any leap year bugs today?
261–270 of 498 posts
Re: Ask HN: Did you encounter any leap year bugs today?
#262Re: Ask HN: Did you encounter any leap year bugs today?
#263Re: Ask HN: Did you encounter any leap year bugs today?
#264We 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…
ChatGPT thinks today is March 1. Go ahead and ask it what today’s date is.
Re: Ask HN: Did you encounter any leap year bugs today?
#265Earlier quoted context omitted.
How do leap day birthdays get handled in general? How is the right age iterated every year?
Sadly, I can say from experience the American draft does not count the number of birthdays celebrated to figure out if you're eligible to serve.
Re: Ask HN: Did you encounter any leap year bugs today?
#266A charge from something I bought today says March 1st.
Re: Ask HN: Did you encounter any leap year bugs today?
#267Re: Ask HN: Did you encounter any leap year bugs today?
#268Earlier quoted context omitted.
How do leap day birthdays get handled in general? How is the right age iterated every year?
Both Feb 28 and Mar 1 are commonly used to celebrate birthdays. AFAIK there is no firm convention. Feb is more natural ("My birthday is in February"), Mar is more logical (the 60th days of the year).
Re: Ask HN: Did you encounter any leap year bugs today?
#269We 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…
ChatGPT thinks today is March 1. Go ahead and ask it what today’s date is.
> You: what is today's date?
> ChatGPT: Today's date is February 29, 2024. Please note that February 29 occurs only in leap years. If you have any more questions or if there's anything else I can help you with, feel free to ask!
Re: Ask HN: Did you encounter any leap year bugs today?
#270Earlier quoted context omitted.
My favorite prompt: asking "How many e's are there in the word egregious". Always says three (ChatGPT 3.5, 4, 4 turbo). When you ask it which three, it realizes its mistake and apologizes (or sometimes tells you where they are that is completely wrong). Looks like it just outputs gibberish for these things.
ChatGPT is specifically bad at these kinds of tasks because of tokenization. If you plug your query into https://platform.openai.com/tokenizer , you can see that"egregious" is a single token, so the LLM doesn't actually see any "e" characters -- to answer your question it would have had to learn a fact about how the word was spelled from it's training data, and I imagine texts explicitly talking about how words are s…
That says it's 3 tokens.