`60 * 60 * 24`
GitHub search for 84600 seconds. Oops.
21–30 of 64 posts
Re: GitHub search for 84600 seconds. Oops.
#22I wonder if Github will ever reconsider allowing bots [0]. There are bunch of things like this that would be cool to have pull-requests automatically generated for. Security fixes would be another place where I can see bots helping to fix common mistakes.
Re: GitHub search for 84600 seconds. Oops.
#23I don't understand.
There will eventually be 84,600 replies to you telling you that there are 86,400 seconds in a day.
Re: GitHub search for 84600 seconds. Oops.
#24check out 48600 seconds for ruby, https://github.com/search?q=48600+seconds&type=Code&ref=sear...
Re: GitHub search for 84600 seconds. Oops.
#25And none of them have any Stars: https://github.com/search?q=84600+seconds+stars%3A%3E0&type=...
Re: GitHub search for 84600 seconds. Oops.
#26A day is not always 24 hours. http://en.wikipedia.org/wiki/Daylight_saving_time
But 24 hours is always 24 hours
Re: GitHub search for 84600 seconds. Oops.
#27Honestly, I think there's a little something to this submission beyond the "Ha ha, lots of people made typos that could cause big problems" factor.
A public repository like GitHub makes checks for common errors like this really easy. Would it be feasible for GitHub or the community to automatically recognize broad classes of these likely errors and notify the authors? How sophisticated could that sort of tool become?
Maybe "given enough bots, most bugs are shallow".
Re: GitHub search for 84600 seconds. Oops.
#28Re: GitHub search for 84600 seconds. Oops.
#29I don't understand.
[deleted]
Re: GitHub search for 84600 seconds. Oops.
#30Many of those are legitimately meant to be 23.5 hours, not 24 hours (TTL defaults, approximates for converting seconds to days, etc.)