A while back I was developing a workflow scheduler. However the run duration kept coming back negative. The runs kept finishing like 15 seconds before they started. Eventually I figured out why; the company had configured a policy to use their custom NTP server, but it was 16.7 seconds off. So my Windows laptop’s time was in the future, but the WSL VM (which ran the program) used another NTP server and was correct. In the end I just added a bodge that made the program request the time from an external server on startup to calculate an offset.

  • HamsterRage@lemmy.ca
    link
    fedilink
    arrow-up
    0
    ·
    15 hours ago

    Whenever I book a flight with Air France, I have to enter our birth dates off by one day. We’re in Canada, and the Air France servers are most likely in…France, or at least using a french time zone.

    Anyways, I figure that someone decided to use some form of LocalTime midnight for the date. We’re 6 or 7 hours later, so when it translates it to French time, it’s a different day.

    So, not a bug that I fixed, but one that I work around. It’s been this way for years, too.