fix: inherit explore default timezone in chat charts without time_zone - #9839
Open
eminemead wants to merge 1 commit into
Open
fix: inherit explore default timezone in chat charts without time_zone#9839eminemead wants to merge 1 commit into
time_zone#9839eminemead wants to merge 1 commit into
Conversation
Explain charts omit time_zone and were binned in UTC. Resolve the same explore default as dashboards, keeping an explicit spec zone authoritative and falling back to UTC when no explore is available.
nishantmonu51
added
Type:Bug
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
time_zonewere always binned in UTC, so day grains did not match the explore default timezone.ChartBlocknow resolves timezone the same way dashboards do: explicit spectime_zone, else the exploredefaultPreset.timezone/ firsttimeZonesentry, else UTC.getDefaultTimeZonehonorsdefaultPreset.timezonefirst. An explicit spec zone stays authoritative.Checklist:
Developed in collaboration with Claude Code