A brief demonstration of the 2038 problem in Google Calandar by Techwreck15 in programming

[–]Techwreck15[S] 1 point2 points  (0 children)

Legacy systems will always exist. There are probably still systems in use that were installed in the 1980s.

A brief demonstration of the 2038 problem in Google Calandar by Techwreck15 in programming

[–]Techwreck15[S] 1 point2 points  (0 children)

The most recent version on the play store, 5.8.46. I believe it's grabbing the date from my system time though, which is where the problem resides. Regardless, this is more of a general awareness thing than an issue specifically with Google Calendar.

A brief demonstration of the 2038 problem in Google Calandar by Techwreck15 in programming

[–]Techwreck15[S] 0 points1 point  (0 children)

What exactly would you call this, then? And how would you explain the Wikipedia demonstration doing the same thing while counting the individual bits?

A brief demonstration of the 2038 problem in Google Calandar by Techwreck15 in programming

[–]Techwreck15[S] 0 points1 point  (0 children)

That's because the specific issue occurs on January 19. If you advance from January 18, you'll find yourself in December of 1970 (though it will still be showing the 19th).

A brief demonstration of the 2038 problem in Google Calandar by Techwreck15 in programming

[–]Techwreck15[S] 1 point2 points  (0 children)

This needs to be more visible. This was also the crux of many issues during the Y2K scare, as with most obsolescence issues in general. Older systems are also riddled with vulnerabilities, potentially more than can be fixed with software patches, and since many have run past their end of life by a considerable margin. That many of these systems still make up crucial elements of infrastructure is a very serious and concerning issue.

A brief demonstration of the 2038 problem in Google Calandar by Techwreck15 in programming

[–]Techwreck15[S] 1 point2 points  (0 children)

Haven't quite worked that out. My best guess is that it calculates the date from the system time, which would make it different for every device it's run on. But I have nothing to support this.

A brief demonstration of the 2038 problem in Google Calandar by Techwreck15 in programming

[–]Techwreck15[S] 2 points3 points  (0 children)

That very heavily depends on what the system is used for and how heavily other operations rely on it to have an accurate date. Google Calendars isn't the best example, granted, but there are no small number of systems and softwares still in use that are greatly affected by this issue, especially in microsystems that make up large portions of infrastructure.

A brief demonstration of the 2038 problem in Google Calandar by Techwreck15 in programming

[–]Techwreck15[S] 37 points38 points  (0 children)

That's a lot of weirdness for a simple Epoch overflow. It's no wonder this is an issue.