fix(anomaly detection): fix historical/current data time window inconsistency #91782
Conversation
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
github-actions
bot
added
the
Scope: Frontend
Codecov ReportAll modified and coverable lines are covered by tests ✅ ✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #91782 +/- ##
==========================================
- Coverage 87.64% 87.64% -0.01%
==========================================
Files 10346 10346
Lines 586180 586179 -1
Branches 22555 22555
==========================================
- Hits 513754 513753 -1
Misses 71981 71981
Partials 445 445 |
ram-senth
reviewed
May 16, 2025
ram-senth
approved these changes
May 16, 2025
ram-senth
approved these changes
May 16, 2025
natemoo-re
approved these changes
May 16, 2025
andrewshie-sentry
pushed a commit
that referenced
this pull request
May 20, 2025
…sistency (#91782) Before sending an anomaly detection request, verify that the historical and current timeseries have the same time window, and verify that the time window is consistent with what the user has specified.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Before sending an anomaly detection request, verify that the historical and current timeseries have the same time window, and verify that the time window is consistent with what the user has specified.