-
-
Notifications
You must be signed in to change notification settings - Fork 259
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
Calculated refresh interval causes the time to drift behind #2
Comments
Hi Detegr, I understand you're running py3status with -n 5 when you speak of the interval. Unfortunately I've been unable to reproduce this behavior. Would you mind giving me:
Thanks |
Ok, I was able to reproduce only when i3status interval is lower than py3status'. I created the drift branch to address this issue. Could you try it please using this commit ? |
Hi. Thanks for looking into the issue this fast. That commit seems to resolve the issue! Works as expected now, thank you :) |
Hi, glad I could fix this problem, thanks a lot for reporting it. I just bumped py3status to v0.7 thanks to you :) |
fix occasional error due to dbus player being removed
Error tweaks - cleanup - thanks a lot for your help @pydsigner .
Error tweaks - cleanup - thanks a lot for your help @pydsigner .
Error tweaks - cleanup - thanks a lot for your help @pydsigner .
Sleep on line 313 causes (at least on my machine) the time on i3status to drift behind. Also, if the interval is set e.g. to 5 seconds, the time advances only one second in one refresh, thus drifting the time behind 4 seconds per one refresh interval.
The text was updated successfully, but these errors were encountered: