Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Job runs time consumption error #89

Open
OpenDGPS opened this issue Jan 13, 2025 · 0 comments
Open

Job runs time consumption error #89

OpenDGPS opened this issue Jan 13, 2025 · 0 comments

Comments

@OpenDGPS
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant