Bug Fix : Fix panic while parsing null timestamps #165
Conversation
This file contains 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
|
Code coverage report for PR #165
|
yaelleC
requested review from
sunker and
fridgepoet
and removed request for
a team
yaelleC
commented
Apr 21, 2022
Comment on lines
+212
to
+214
| if datum.ScalarValue == nil { | ||
| return nil, nil | ||
| } |
There was a problem hiding this comment.
This is the bug fix, the rest of the changes are test-related
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When Timestream returns null timestamps, we get a panic error from the parser, I added a check for it.
Fixes #162