Fix: Ensure Timestamp Parsing Rejects Characters After 'Z #5189
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
tustvold
approved these changes
Dec 7, 2023
|
Looks good to me, thank you |
razeghi71
force-pushed
the
fix/timestamp-post-Z-validation
branch
from
23f024e to
7f1edde
Compare
razeghi71
force-pushed
the
fix/timestamp-post-Z-validation
branch
from
7f1edde to
d110fa7
Compare
|
Thank you @razeghi71 |
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.
Which issue does this PR close?
Closes #5182
What changes are included in this PR?
I have changed the
string_to_datetimeto make sure that the 'Z is always the last charachter.Are there any user-facing changes?
No