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

Notice: offset in logged timestamps #180

Open
ghost opened this issue Feb 21, 2018 · 1 comment
Open

Notice: offset in logged timestamps #180

ghost opened this issue Feb 21, 2018 · 1 comment

Comments

@ghost
Copy link

ghost commented Feb 21, 2018

I've noticed that there is an offset in the timestamps logged in the output file.

This seems to be caused because the next event's timestamp is written in the output file right after an event's happening, even if the next event is to happen several minutes/hours/days later.

Logging started ...

2018-02-16 20:24:21+0000 > Logging started ...

2018-02-20 19:08:12+0000 > 03458263 <-scanned the 20
2018-02-20 19:08:29+0000 > 03458263 <-scanned the 20
2018-02-20 19:08:32+0000 > 03458263 <-scanned the 21 but timestamp written the 20 
2018-02-21 18:16:50+0000 > 03458263 <-scanned the 21
2018-02-21 18:17:24+0000 > <-timestamp already written in file, even if the event haven't happened yet

This is not an actual issue nor a source of great imprecision (if we are aware of it) but i still think this could be adressed easely (at first glance).

Best regards

@kernc
Copy link
Owner

kernc commented Feb 22, 2018

Yeah, the timestamp is printed when Enter key is pressed.

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