-
Notifications
You must be signed in to change notification settings - Fork 298
reject non-RFC3339 timestamp strings in timestamp() conversion #1338
New issue
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
Open
alhudz
wants to merge
4
commits into
cel-expr:master
Choose a base branch
from
alhudz:timestamp-rfc3339-strict
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+175
−1
Open
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
98e5600
reject non-rfc3339 timestamp strings in timestamp() conversion
alhudz a6f83c3
return early with a specific error when the timestamp format is invalid
alhudz ea57bf4
add benchmark for timestamp() string conversion
alhudz 2e16e64
replace RFC 3339 regex gate with a hand-rolled scan
alhudz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prefer early return on an error for an invalid format as this will provide a more helpful message to the user (or agent).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. The pattern check now returns early with
invalid RFC 3339 timestamp "<value>"rather than falling through to the generic conversion error, and the regression test asserts the exact message for each rejected form.go test ./...still passes.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you mind adding a little benchmark to see the perf impact of the regex?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added
BenchmarkStringConvertToTimestampover the conversion path. On an M4, converting a valid2025-01-01T12:34:56.123456789Zruns around 600 ns/op at 1 alloc/op. The regexMatchStringis the bulk of that (~500 ns/op, 0 allocs) against ~90 ns/op for the baretime.Parse, so the gate adds no allocations but does roughly 6x the parse cost. Happy to swap the regex for a small hand-rolled scan if that overhead matters on the hot path.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you wouldn't mind a small hand-rolled scan. I looked into it a bit and it's doable, but roughly 100-ish lines ... seems easy to conformance test against the regex though, so maybe keep the regex for testing purposes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. The conversion path now goes through a hand-rolled
isStrictRFC3339scan instead of the regex. KeptstrictRFC3339Patternas the reference and addedTestIsStrictRFC3339MatchesPatternwhich asserts the scan and the regex agree across the field boundaries (hour/minute/second/offset edges, leap second, comma separator, single-digit fields, missing/empty zone).The scan is allocation-free and roughly an order of magnitude cheaper than the regex
MatchStringon the same machine, so the gate no longer dominates the convert.go test ./...passes.