The FIP-FS “Microsoft” Scan Engine Failed. Can’t Convert “2201010001” to Long

https://twitter.com/miketheitguy/status/1477097527593734144

by doomlaser • 5 years ago

43 11 5 years ago

twitter.com

fredley• 5 years ago

Given all the y2k fuss how did they not see this one coming?

Jare• 5 years ago

Rest assured, by 2038 we'll have it all properly figured out

hughrr• 5 years ago

As per the millenium bug timeline, I suspect we won't start worrying about it until about September 2037...

I remember someone running into our office and asking if anyone knew Z80 assembly.

Freak_NL• 5 years ago

Perhaps someone back in 1999 figured that 2022 was so incredibly far in the future (and way past their retirement), there was no way that codebase would still be allowed in operation. Flying cars and world peace and all.

Taniwha• 5 years ago

For the record 2201010001 (ie today's date) is greater than the largest 32-bit signed int (while 2112310001 wasn't)

_dain_• 5 years ago

Why on earth do they store it like that?

stillicidious• 5 years ago

The codebase is from at least 1996.

breakingcups• 5 years ago

leni536• 5 years ago

Maybe we should have full test networks that run a full year in the future to catch various date bugs ahead of time. The problem is that you probably can't connect it to the Internet.

tgv• 5 years ago

Their code base may be old, but their twitter handle is on point.

The FIP-FS “Microsoft” Scan Engine Failed. Can’t Convert “2201010001” to Long

Related Stories