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

timestampAfterCurrentOne.Sub(timestampCurrent).Seconds() < 0 detected very often #30

Closed
JeremyTheocharis opened this issue Jan 18, 2021 · 0 comments · Fixed by #31
Closed
Assignees
Labels
type: bug Something isn't working

Comments

@JeremyTheocharis
Copy link
Member

The error message timestampAfterCurrentOne.Sub(timestampCurrent).Seconds() < 0 appears quite often. It is hard to debug.

Expected Behavior

Normally there should not be any errors while executing.

Current Behavior

The error message appears quite frequently and it is hard to debug and to describe it. At least add additional information.

@JeremyTheocharis JeremyTheocharis added type: bug Something isn't working factoryinsight labels Jan 18, 2021
@JeremyTheocharis JeremyTheocharis self-assigned this Jan 18, 2021
@JeremyTheocharis JeremyTheocharis linked a pull request Jan 18, 2021 that will close this issue
JeremyTheocharis added a commit that referenced this issue Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant