Bug when switching between normal and daylight-saving time

[notting]

Hi!

Couldn't find a similar thread.
Originally: FAH 7.6.13 running on Win10.

My computer was shut down over night, so it was completely switched off. When I booted this morning, it didn't switch back automatically from daylight-saving to normal time (CEST -> CET) as it should. I noticed that while FAH was processing WUs. The WUs were processed in finishing mode because I wanted to update to FAH 7.6.21 while there aren't any jobs running.
I went to the Windows time settings and switched off automatically time setting via internet and on again. Then the time was correct. Some time later I noticed that completely unrealistically the FAH WUs where hanging at ca. 99%. The FAH Windows client didn't work, even not the context menu of the FAH icon next to the Windows clock in the taskbar. But the web-interface worked. I stopped the jobs. Then the percentage values jumped back to realistic values.

Then I wanted to update to FAH 7.6.21. But the setup hang in a quite early stage. It only continued after I killed FAHClient.exe via task-manager.
Now everythings seem to work again.

Are these bugs known?

cu

notting

[PantherX]

The issue of the WU progress showing 99% but not really at 99% is a known bug: https://github.com/FoldingAtHome/fah-issues/issues/1240

I do know that if the time zone changes, there will be a message about time skew printed in the log. Considering the events, (time change -> 99% bug -> upgrade after hung fahclient.exe), I am tempted to say that it was a series of unfortunate events being triggered by the time zone change.

[notting]

The issue of the WU progress showing 99% but not really at 99% is a known bug: https://github.com/FoldingAtHome/fah-issues/issues/1240

I do know that if the time zone changes, there will be a message about time skew printed in the log. Considering the events, (time change -> 99% bug -> upgrade after hung fahclient.exe), I am tempted to say that it was a series of unfortunate events being triggered by the time zone change.

Thanks. Hopefully it will help other people having such problems.

notting

[MeeLee]

Yeah, to not move your pc right between timezone when folding!
But if you do, you could save an hour off of WUs, and probably get higher PPD for that, I don't know...

[Joe_H]

As best as I can tell, the bug only effects the display of estimates, it won't change the real PPD. That is one of the reasons all times are in UTC, no changes back and forth for daylight savings.

[PantherX]

That's correct, changing the local time on your system will not cause any increase in points since they are calculated based on when the WU was assigned and when it was returned (that information is on the Server itself). If you change your time dramatically, you might be dumping a WU if it has reached the expiry time even though in real-life, there's more time.

Most of the time, the clock skew message is printed and the WU carries on as long as the expiration date hasn't been reached.

[bruce]

That's correct, changing the local time on your system will not cause any increase in points since they are calculated based on when the WU was assigned and when it was returned (that information is on the Server itself). If you change your time dramatically, you might be dumping a WU if it has reached the expiry time even though in real-life, there's more time.

The servers and FAHClient all operate on UTC (formerly GMT) and it does not have seasonal time zone changes (even though much of the world (including BST) do switch twice a year.