fix(events): Account for project timezone in absolute range EventsQuery
#25832
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.
Problem
Reported in ZEN-19450: Absolute date ranges were always effectively treated as UTC in
EventsQueryRunner
. This was off for projects with a non-UTC timezone set.Changes
We were using raw
isoparse()
, whererelative_date_parse()
already handles both absolute and relative datetimes correctly accounting for timezones. The fix is simply removing the needlessisoparse
.How did you test this code?
Added a test case that fails on master and passes here.