Repository navigation
fix(core): return 400 instead of 500 on malformed time ranges in temporal filters (#45459) #45822
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
FrancescoCastaldi
wants to merge
3
commits into
apache:master
Choose a base branch
from
FrancescoCastaldi:fix/temporal-filter-invalid-time-range-400
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.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
15de192
fix(core): return 400 instead of 500 on malformed time ranges in temp…
FrancescoCastaldi e74e08b
fix(core): address review feedback from @sadpandajoe on temporal filt…
FrancescoCastaldi 089c8d3
fix(core): catch TypeError on mixed-timezone temporal ranges and form…
FrancescoCastaldi 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
Oops, something went wrong.
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.
A secondary temporal filter like
"2024-01-01T00:00:00Z : 2024-01-02"still returns a 500:get_since_untilcompares an offset-aware_sincewith a naive_until(_since > _until) and raisesTypeError, which isn't in this tuple, so it escapes the new handler. The same gap applies to the other guards added here. ShouldTypeErrorbe caught too, or is mixed-timezone input intentionally out of scope for this fix?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.
In commit
089c8d37a4, we addressed this by addingTypeErrorto the caught exception tuple across all threeget_since_until_from_time_rangecall sites insuperset/models/helpers.py(lines 3089, 3227, and 7027). When mixed offset-naive and offset-aware datetimes like"2024-01-01T00:00:00Z : 2024-01-02"are passed,get_since_untilraises aTypeErrorduring timestamp comparison (_since > _until). This is now properly intercepted and converted into aQueryObjectValidationError, consistently returning 400 instead of 500.Additionally, we formatted the exception statement in
superset/models/helpers.pyto satisfyruff-format(resolving thepre-commit (current)CI failure) and added a dedicated regression unit test intests/unit_tests/models/helpers_test.pyverifying mixed-timezone temporal ranges.