I thought that this was going to be different story. There was a program I heard about back in the 90s which would literally crash depending on the phase of the moon! The story is that it wanted to print a date. The programmer happened to have an astronomy library available that gave a string containing the date. So the programmer called that, and then parsed out the date. Unfortunately the astronomy library wrote it…
The code worked differently when the moon was full
21–30 of 175 posts
Re: The code worked differently when the moon was full
#22The problem was that they lived on the coast, and a subsurface junction box would get wet during king tides, causing the telephone line to fail.
Re: The code worked differently when the moon was full
#23Nobody could figure it out so they called in an expert.
After lots of attempts and figuring, one day the person in question happens to look out the window at the time in question ... and sees a service truck park exactly in line-of-sight between the business and their internet-signal pickup broadcast point.
Ah ha!
Re: The code worked differently when the moon was full
#24Re: The code worked differently when the moon was full
#25Re: The code worked differently when the moon was full
#26Re: The code worked differently when the moon was full
#27Re: The code worked differently when the moon was full
#28The most notable exception would be languages which allow negative indexing, but IMHO if that were syntactic instead of relying on actual signed integers, it would be safer (I.e., [- $int] would be a different syntax from [(-$int)] and the latter would not be correctly typed.)
Re: The code worked differently when the moon was full
#29> Bugs based on a time calculations can often show themselves later when view through a longer lens and scope of time...sometimes WAY longer than you'd expect. When I worked for BBN in '97-'98, someone from outside the company as I recall came to talk to a room of engineers about the wide variety of calendar-related behaviors in various UNIX systems that were expected to cause problems for Y2K. It was a very, very lo…
Dates are a pain. The date bug I committed with the longest tail was daylight time. It was all good until we got to a day with 25 hours when we "fell back."
Re: The code worked differently when the moon was full
#30Reminds me of a story where a company's internet would regularly drop at the same time every day -- let's say 3pm. Nobody could figure it out so they called in an expert. After lots of attempts and figuring, one day the person in question happens to look out the window at the time in question ... and sees a service truck park exactly in line-of-sight between the business and their internet-signal pickup broadcast poi…
why this would occur i'll never know. (probably old telephone wiring wrapped around old 110v wiring? maybe? or who knows what kind of weird leakage/ground loops may have existed)