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.

Sign up for GitHub

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

Jump to bottom

time.elapsed is a timestamp when idle, but a timespan when running #11

Closed
gwh-cpnet opened this issue Aug 1, 2019 · 4 comments
Closed

time.elapsed is a timestamp when idle, but a timespan when running #11

gwh-cpnet opened this issue Aug 1, 2019 · 4 comments
Labels
bug

Comments

@gwh-cpnet
Copy link

Is it on purpose?

from my point of view, time.elapsed should be 0 when its state is idle. Anyway, put them into the same variable looks weird.
@onury onury added the bug label Aug 1, 2019
@onury
Copy link
Owner

onury commented Aug 1, 2019

No. That's a bug. Good catch actually.
Thanks.

@onury
Copy link
Owner

onury commented Aug 1, 2019

Bug demonstration: https://runkit.com/onury/tasktimer-issue-11

@onury onury closed this as completed in c43c1a2 Aug 2, 2019
@onury
Copy link
Owner

onury commented Aug 2, 2019

Fixed in v3.0.0

@gwh-cpnet
Copy link
Author

Thanks for clarifying and quick fix.

@gwh-cpnet gwh-cpnet mentioned this issue Aug 2, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@onury @gwh-cpnet