Fix timestamp #338
Merged
Fix timestamp #338
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
A follow-on patch will regenerate Make-managed files. Signed-off-by: Alex Nelson <[email protected]>
Signed-off-by: Alex Nelson <[email protected]>
Member
Author
|
This PR is ready for review and merge. |
kchason
approved these changes
Nov 14, 2025
vulnmaster
approved these changes
Nov 14, 2025
Contributor
vulnmaster
left a comment
vulnmaster
left a comment
There was a problem hiding this comment.
2nd review after Keith. Everything looks good.
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.
It seems
xsd:dateTimesyntax is reviewed a little more stringently in Python 3.14. Testing in another repository that pulls in the CASE website's examples caught a timestamp that goes sub-second without specifying a second. This PR fixes the syntax.