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

Statistics, strange remaining time calculation #652

Open
berti34 opened this issue Jan 24, 2025 · 4 comments
Open

Statistics, strange remaining time calculation #652

berti34 opened this issue Jan 24, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@berti34
Copy link

berti34 commented Jan 24, 2025

Describe the bug
Refreshing stats on a slow x64-Linux notebook starts with negative time and later it seems to switch to normal

To Reproduce
Go to repo view and start by click on "Index Snapshots" and "Compute Stats"

Expected behavior
Calculate statistics

Screenshots
Image

Image

Image

Image

Image

Platform Info

  • OS and Architecture
    Linux, Manjaro Arch, x64

  • Backrest Version
    1.7.1

Additional context
That machine is the only one with that behavior.
Other Laptops and Raspis are doing right with the same rest-server-Repository.

Additionally a template error appears after killing the job.

@berti34 berti34 added the bug Something isn't working label Jan 24, 2025
@berti34
Copy link
Author

berti34 commented Jan 24, 2025

The laptop's clock is 7 minutes ahead the browser time. It seems that this is the source of the problem.

@garethgeorge
Copy link
Owner

Thanks @berti34 , this is likely correct. Backrest does rely on the server's and client's times being synchronized correctly to universal time, some strange UI bugs of this sort are prone to showing up when they are not.

@berti34
Copy link
Author

berti34 commented Feb 17, 2025

Hi @garethgeorge

so this is ok for you and the behaviour will not be changed in a future release?

For me this is not very important, in opposite of the template bugs #670 #635 and #527

Greatings from Germany

@garethgeorge
Copy link
Owner

I think this is relatively low priority as you say, a good fix might be for backrest to include some clock synchronization but it adds a good amount complexity. Not sure how worthwhile it is to fix.

Ideally system clock synchronization is accurate within a second or so in most cases.

Agree that the nil ptr bugs are higher priority, should be fixed in 1.7.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants