5 ms·
When would you ever need a timer for 724 years?
by zatkin 4y ago
When would you ever need a timer for 724 years?
- paxys 4y agoA bug is a bug. "Why would anyone ever do XYZ" is a separate discussion. And if you write software for a living you know that there is always that one user who will do exactly XYZ.
- bbertelsen 4y agoHyrum's law. How meta.
- kuboble 4y agoNope. Undefined behavior on obviously incorrect input isn't a bug in my world. ( might be in other circumstances )
- taftster 4y agoYou must be a C programmer.
- insightcheck 4y agoHaha. I was thinking along similar lines as kuboble, but then I'm someone in the process of trying to learn C. I agree, upon further thought, that at least an error message would be better for the user (e.g. "Maximum timer duration exceeded").
- dogecoinbase 4y ago"Undefined behavior consists of exactly one proposition, to wit: There must be compiler engineers whom the language standard protects but does not bind, alongside developers whom the language standard binds but does not protect." (source: https://twitter.com/jckarter/status/1558181259314167808 https://twitter.com/jckarter/status/1558181259314167808 )
- diarrhea 4y agoI mean, the query is “timer $period”. It’s correct in its syntax, a period’s a period. It’s not asking for “timer TIMMY; DROP TABLES”. That’s incorrect input.
- nomel 4y agoIt's not incorrect input. It's incorrect handling of accepted input.
- JohnFen 4y agoUndefined behavior on obviously incorrect input is always a bug. Incorrect input should give you an error.
- sverhagen 4y agoSure, a bug is a bug, but the original remark was that the software was "buggy". I read "buggy" as riddled with pretty obvious bugs. If we're calling software "buggy" for having any bugs, then, I guess, nearly all software is "buggy" (and the word looses its usefulness).
- Jtsummers 4y agoAnything over 100 hours gets recalculated modulo 100, so 101 hours becomes 1 hour. But then the page title, which is meant to show the current countdown in the tab display, gets updated to show the full time, but weirdly formatted. So at least two bugs. Try "timer 101 hours". The page title will (very quickly) show "10:05:9x" where x is the 10s digit of the seconds. While the page itself claims it's a one hour timer (59 minutes and some seconds). So the actual time is in there somewhere, just showing up wrong in both places. It also doesn't seem to let me enter 30 minutes as a timer, but most other minutes times work. So, yes, it's buggy. EDIT: It's not actually modulo 100 hours, I should note. The display is showing it that way, but since it has the real time stored internally it still counts down. If it were actually modulo 100 hours then it would zero out a 100 hour (or 200 or 300...) countdown immediately, instead these wrap to 99 hours, 59 minutes, and 59 seconds on the first tick. EDIT: For grins I'd started a 101 hour timer a bit over an hour ago before stepping away from the computer. Despite the display silliness, it actually will run for 101 hours. After the first hour the displayed time rolls back to 99:59:59 and the page title updates correctly. I also noticed that there's a progress bar below the timer, it correctly shows the progress within the 101 hour timer the whole time.
- sverhagen 4y agoThose sound like reasonable bugs, the original that we were responding to (724 years), less so.
- benbristow 4y agoWhen you're waiting for the answer to life, the universe and everything
- deleted 4y ago[deleted]
- efsavage 4y ago724 Test Engineers walk into a bar...
- anonu 4y agoMaybe to be reminded that were about 7% of the way through the life of the 10,000 year clock? https://www.10000yearclock.net/learnmore.html https://www.10000yearclock.net/learnmore.html
- Tepix 4y agoDid they finish building it?