Job runs time consumption error #89
Description
The calculation of "seconds since last update" in Progress.jsx can be wrong if the server and the users browser are in different timezones. Depends on the difference of these TZs an offset is added to the real time delta. This can also happen if the server is running locally on docker as in some setups UTC is use by default.
In this case the browser is running with UTC+2 and the container with UTC. In result it shows something like "36002 seconds since last update" if it is in reality only two seconds.
The server sends it's own datetime.now() in latentscope/server/jobs.py and the client gets the timestamp in web/src/components/Job/Progress.jsx.