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

Calculated refresh interval causes the time to drift behind #2

Closed
Detegr opened this issue Apr 5, 2013 · 4 comments
Closed

Calculated refresh interval causes the time to drift behind #2

Detegr opened this issue Apr 5, 2013 · 4 comments
Assignees
Labels
bug 😞 I am reporting a bug

Comments

@Detegr
Copy link

Detegr commented Apr 5, 2013

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.

@ultrabug
Copy link
Owner

ultrabug commented Apr 5, 2013

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:

  • the version of python you're using
  • the global configuration part of your i3status.conf

Thanks

@ghost ghost assigned ultrabug Apr 5, 2013
@ultrabug
Copy link
Owner

ultrabug commented Apr 5, 2013

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 ?

@Detegr
Copy link
Author

Detegr commented Apr 6, 2013

Hi. Thanks for looking into the issue this fast. That commit seems to resolve the issue! Works as expected now, thank you :)

@ultrabug
Copy link
Owner

ultrabug commented Apr 6, 2013

Hi, glad I could fix this problem, thanks a lot for reporting it. I just bumped py3status to v0.7 thanks to you :)

@ultrabug ultrabug closed this as completed Apr 6, 2013
tobes pushed a commit that referenced this issue Sep 2, 2016
fix occasional error due to dbus player being removed
lasers referenced this issue in lasers/py3status Nov 18, 2017
Error tweaks - cleanup - thanks a lot for your help @pydsigner .
lasers referenced this issue in lasers/py3status Dec 14, 2017
Error tweaks - cleanup - thanks a lot for your help @pydsigner .
ultrabug pushed a commit that referenced this issue Dec 20, 2017
Error tweaks - cleanup - thanks a lot for your help @pydsigner .
lasers added a commit that referenced this issue Feb 7, 2019
lasers added a commit that referenced this issue Feb 7, 2019
lasers added a commit that referenced this issue Feb 7, 2019
lasers added a commit that referenced this issue Feb 9, 2019
lasers added a commit that referenced this issue Feb 10, 2019
ultrabug pushed a commit that referenced this issue Feb 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 😞 I am reporting a bug
Projects
None yet
Development

No branches or pull requests

2 participants