Leon Blackwell
Paul DwerryhouseY2k38 problems starting to show up early:
https://www.calendar-australia.com/holiday/easter-sunday/4-20-2025/
Edwin Groothuis@pdwerryhouse Oh that is a beauty!
David Fi&er
The Doctor
JZP@pdwerryhouse We were *joking* in 1999 about this. Stunning.
Sivation@pdwerryhouse show up publically at any rate - FinTech have had to deal with this for some time now. Pricing bonds to maturity when said bonds are 30+ years long....
BEOZ@pdwerryhouse The year in Australia starts 2038 with Easter Sunday on a Friday. Sounds great 😁
https://www.calendar-australia.com/holidays/2038/
#y2k38
https://www.calendar-australia.com/holidays/2038/
#y2k38
Yohan Yukiya Sese Cuneta 사요한🦣@pdwerryhouse I've been hoping to witness another #Y2k I guess it'll come true soon. ^_^;;
I wonder if #Y2k38 isn't “fixed” by then, are we going to see something similar to 1999? It was an opportunity for many to make some money, LOL. And companies, who ignored it, panicked in '99.
Mike MacgirvinThis should only be affecting 32-bit webservers - I doubt we'll have very many of these left in 2038.
wiredog
Steve@pdwerryhouse Is it though?
"Attempting to increment to the following second (03:14:08) will cause the integer to overflow, setting its value to −(231) which systems will interpret as 231 seconds before epoch (20:45:52 UTC on 13 December 1901)"
"Attempting to increment to the following second (03:14:08) will cause the integer to overflow, setting its value to −(231) which systems will interpret as 231 seconds before epoch (20:45:52 UTC on 13 December 1901)"
GantSentinel@pdwerryhouse Figured most admins would have patched this sh!t by now. Sign the damn dates in a 64-Bit integer.
Jernej Simončič �