My "smart"watch froze at 23:59 28th Feb
Ask HN: Did you encounter any leap year bugs today?
361–370 of 498 posts
Re: Ask HN: Did you encounter any leap year bugs today?
#362Surprised no one else mentioned the Cloudflare billing issue today. I got incorrectly invoiced yesterday and the file was named cloudflare-invoice-1970-01-01.
Re: Ask HN: Did you encounter any leap year bugs today?
#363Earlier quoted context omitted.
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…
> If you plug your query into https://platform.openai.com/tokenizer , you can see that"egregious" is a single token That says it's 3 tokens.
[deleted]
Re: Ask HN: Did you encounter any leap year bugs today?
#364Earlier quoted context omitted.
Blows my mind that people consider using ChatGPT for serious applications. I mean it's fine as a code autocorrect/autocomplete tool as in GitHub copilot. But it should not replace the code itself. You encounter a bug in the code, you fix it, you never encounter it again. But ChatGPT will repeat the same mistake sooner or later. That's not how we should engineer solution for critical problems.
If the cost-savings is worth it compared to the problems... I mean, that's how we do it with humans. It's quite a common occurrence to keep a part of a business process human because automating it would we too expense due to edge cases. Humans make mistakes and are expensive, but are also flexible and usually smartish. ChatGPT makes mistakes and is usually dumbish, but is also flexible and cheap. Engineering is about…
>I mean, that's how we do it with humans. It's quite a common occurrence to keep a part of a business process human because automating it would we too expense due to edge cases.
Which part of the human do people keep? The head? Arms? ;)
#ParsingAmbiguityError
Re: Ask HN: Did you encounter any leap year bugs today?
#365Earlier quoted context omitted.
> If you plug your query into https://platform.openai.com/tokenizer , you can see that"egregious" is a single token That says it's 3 tokens.
The number of tokens depends on context; if you just entered 'egregious' it will have broken it into three tokens, but with the whole query it's one.
Why three tokens, not one?
Re: Ask HN: Did you encounter any leap year bugs today?
#366The 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.
https://www.askamanager.org/2018/01/i-paid-for-fake-referenc...
You're not alone!
Re: Ask HN: Did you encounter any leap year bugs today?
#367My 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.
Re: Ask HN: Did you encounter any leap year bugs today?
#368Yes - 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.
I can also never remember if "leap year" means 29 days or 28 days, and which one is normal. I probably checked that twelve times this week. And I was mildly surprised when I noticed that March 1 was Friday and not Thursday...
As a child I somehow always forgot and thought 27 was normal, and then one year the calendar in our kitchen showed 29 days. that was kinda confusing.
Re: Ask HN: Did you encounter any leap year bugs today?
#369We did but I only learned of it today! Completely broke a lot of systems until they set the day to March 1st and back
Re: Ask HN: Did you encounter any leap year bugs today?
#370Earlier quoted context omitted.
Is March more logical? Feb 29 + 1 year = Feb 28.
You're begging the question. [1] "Feb 29 + 1 year" is verbatim restatement. --- You can say Feb 29 + 365 days = Feb 28. (And Feb 29 + 730 days = Feb 27.) --- EDIT: Note that in the context of birthdays, people use "calendar years," not "unit of time which is ~1 revolution around the sun." Birthdays aren't celebrated every X million seconds after the moment of birth. They are celebrated the same day each calendar year…
[deleted]