We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The error message timestampAfterCurrentOne.Sub(timestampCurrent).Seconds() < 0 appears quite often. It is hard to debug.
timestampAfterCurrentOne.Sub(timestampCurrent).Seconds() < 0
Normally there should not be any errors while executing.
The error message appears quite frequently and it is hard to debug and to describe it. At least add additional information.
The text was updated successfully, but these errors were encountered:
Merge pull request #31 from united-manufacturing-hub/JeremyTheocharis…
afeb18f
…/issue30 Fixes #30
0.1.0 (#55)
2ba55f8
Fixes #29 #30 #31 #33 #34 #35 #44 #45
JeremyTheocharis
Successfully merging a pull request may close this issue.
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.
The text was updated successfully, but these errors were encountered: