FabMo
Job manager's relative timestamp for jobs is wrong
That is very odd. Never seen that one before! Keep an eye on it and post here if it happens again, ill do the same.
On Wed, Jun 15, 2022, at 11:58 AM, Kyle Kingsbury wrote:
That is very odd. Never seen that one before! Keep an eye on it and post here if it happens again, ill do the same.
One possible guess (not based on looking at the code): If that timestamp is based on a pi-side date but converted to a relative timestamp by client-side js and the pi can't get to the public internet, its clock could be wrong, resulting in that kind of skew.
— Reply to this email directly, view it on GitHub https://github.com/FabMo/FabMo-Engine/issues/929#issuecomment-1156819593, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALC2B24YWA27QMCMORDNDVPIRWTANCNFSM5YLBYOMA. You are receiving this because you authored the thread.Message ID: @.***>
This problem mostly goes away when the pi is connected to the internet. But only mostly. In this case, my laptop's clock is a couple seconds off from the pi's, letting me execute jobs from the future.
