loopdb: fix timestamp parsing #619
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bhandras
reviewed
Aug 8, 2023
sputn1ck
force-pushed
the
fix_faulty_timestamps
branch
from
f4b4d06 to
5cafa34
Compare
guggero
approved these changes
Aug 8, 2023
Contributor
guggero
left a comment
guggero
left a comment
There was a problem hiding this comment.
tACK, node starts up correctly again.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes how the timestamp parsing is managed, by allowing timestamps to be displayed with nanoseconds.
Additionally we now try both timestamp parsing functions on any given string.