Last Updated timestamp can be in the future

[AlexHeylin]

The Last Updated timestamp at the top of the diags results pane can show a timestamp which has not occurred yet (is in the future).

Example

In this example all machines (guest, host, & server) are in the same timezone Europe/London (GMT +00:00) and that timezone is currently not observing DST. The Last Updates timestamp is 2022-01-31 18:28:56, but the current time is 2022-01-31 18:03 - so the Last Updated timestamp hasn't yet occurred. This logic cannot be correct.

I've not managed to trace the cause of this yet, but I'm opening this issue to track it.

[AlexHeylin]

This seems to be getting worse! I do intend to work on this when time allows.

I've also observed that clicking Run CWA Diagnostics often causes the timestamp to immediately jump forward by a few seconds or so. Surely the timestamp should be the timestamp of the result - not the command being sent. A command being sent doesn't guarantee a result was obtained.