Software Update

Unfortunately It's something that just happens.

I wish they would rename upgraded files like this to something else so way this does not happen.

So the Java file is named javafilev2 instead of javafile. So this was in a new update the system looks for a pulls javafile2 instead of the old javafile one.

This is on thing that stinks about caching. ;)
 
Unfortunately It's something that just happens.

I wish they would rename upgraded files like this to something else so way this does not happen.

So the Java file is named javafilev2 instead of javafile. So this was in a new update the system looks for a pulls javafile2 instead of the old javafile one.

This is on thing that stinks about caching. ;)
No Problem Scott ....
It May have already found the correct file as I haven't see the error since, keep in mind it's only been a short time.
 
No Problem Scott ....
It May have already found the correct file as I haven't see the error since, keep in mind it's only been a short time.
I saw the issue with the times that Foxbat had yesterday but upon a page refresh or two things were back to normal. :)
 
I saw the issue with the times that Foxbat had yesterday but upon a page refresh or two things were back to normal. :)
Yes, a refresh made everything here good as well. iPadOS v18.3.1 and the current Safari client. I figured it was a weird caching issue...

edit: and it just happened to my new Mac Mini with Sequoia v15.3.1 and Safari Version 18.3 (20620.2.4.11.5). A Command-R to refresh and it had the correct time, not "later today at x" (which sounds like Elon and his DoGE Hounds have injected a redirect to X)(JK)
 
  • Like
Reactions: charlesrshell
New wrinkle: it started by saying "tomorrow_at_x" and when I went to get a screen capture, changed to "later_today_at_x". It definitely sounds like a Clock issue. Is there server in the right Time Zone? Is the board properly set up for Eastern Standard Time? Or, is the clock maybe behind a few minutes and the Client Clock tries to resolve the Post Time and it's in the future.

Or, like TRG suggested, is it in orbit around a black hole and proceeding at a slower pace than the rest of SpaceTime? ;)

Here's another clue: it seems to happen most when I click on the Reaction Alert (so-and-so Liked your post). See:
1740426683552.png
 
  • Like
Reactions: charlesrshell
New wrinkle: it started by saying "tomorrow_at_x" and when I went to get a screen capture, changed to "later_today_at_x". It definitely sounds like a Clock issue. Is there server in the right Time Zone? Is the board properly set up for Eastern Standard Time? Or, is the clock maybe behind a few minutes and the Client Clock tries to resolve the Post Time and it's in the future.
1740427475842.png
 
Is the board properly set up for Eastern Standard Time?
The forum runs on whatever your forum account locale is set for (Eastern, Central, Mountain, Pacific, Hawaii, etc.).

I'd imagine that everything is referenced to GMT (as many modern servers are because GMT never suffers Daylight Savings jumps) and the user locales take care of any conversions. I can't see a properly coordinated date showing up in the future unless there's some bad PHP code that ignores the time zone offset established by the locale.

Most properly configured Linux servers get their time from the ntp utility once the system is up and running and that works around any settings with the RTC of the mainboard. Another utility, ntpdate is used to set the RTC and system time on a one-shot basis but that's typically not very useful for a system that ideally never reboots.

Windows will fail to update the clock using NTP if the BIOS date is too far off but I don't think ntp cares about any differential that might exist.
 
  • Like
Reactions: charlesrshell
Top