4 ms·
I committed a 2038 bug probably 25 years ago. A salesman found it the hard way fat-fingering a job into the 2060s. You don't have to reach the trigger date to
by LorenPechtel 5y ago
I committed a 2038 bug probably 25 years ago. A salesman found it the hard way fat-fingering a job into the 2060s. You don't have to reach the trigger date to set these things off, anything that looks to the future can trip them.
(I knew it wouldn't work past 2038, I didn't realize it would keep anyone from seeing the production schedule if it contained an offending job.)
- throwawayboise 5y agoAny code dealing with 30-year mortgages or bond maturities has had to deal with this since at least 2008.
- Piskvorrr 5y agoYup. Working with long-term...contracts...in a database, this has brought us considerable panic then. 30-year default expiration, indeed.