-
Notifications
You must be signed in to change notification settings - Fork 933
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
[BUG] Dashboards crashes when time filter is out of range #911
Labels
bug
Something isn't working
Comments
AMoo-Miki
pushed a commit
to AMoo-Miki/OpenSearch-Dashboards
that referenced
this issue
Feb 10, 2022
AMoo-Miki
pushed a commit
to AMoo-Miki/OpenSearch-Dashboards
that referenced
this issue
Feb 10, 2022
# [24.2.0](elastic/elastic-charts@v24.1.0...v24.2.0) (2020-11-25) ### Bug Fixes * near and far alignments for orthogonal rotations ([opensearch-project#911](elastic/elastic-charts#911)) ([6b162c6](elastic/elastic-charts@6b162c6)) ### Features * add projection click listener ([opensearch-project#913](elastic/elastic-charts#913)) ([19c14e4](elastic/elastic-charts@19c14e4)), closes [opensearch-project#846](elastic/elastic-charts#846)
I was unable to reproduce this in the current version of the OpenSearch Dashboards playground: |
But I do think we should re-examine the bounds checking and handling in the date range filter - it's weird that you can (for example) set both the start and end time to the future. And there is also inconsistency in the error handling and rendering of various visualization types. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A clear and concise description of what the bug is.
Opensearch Dashbaords crashed when entering a time range (filter) beyond ~10k years.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Show an error message like "time out of range"
OpenSearch Version
1.0
1.1
Dashboards Version
1.0
1.1
Screenshots
Host/Environment (please complete the following information):
Additional context
As discussed on Discord Opensearch unofficial
The text was updated successfully, but these errors were encountered: