This repository has been archived by the owner on Sep 12, 2024. It is now read-only.
release: v0.10.1 #1084
Merged
release: v0.10.1 #1084
Conversation
This file contains 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 change makes the values in the dropdown in FE sorted too.
- when api endpoint is triggered, the run_anomaly flag is set to false - run_anomaly is set to false when KPI is created - run_anomaly set to true when anomaly is configured - run_anomaly set to false when analytics is disabled - Changes in logic to incorporate the above in the digest_controller, analytics_scheduler, kpi_view, anomaly_data_view
Also removes one extra line of code
feat(enable-anomaly): enables an anomaly by modifying the run_anomaly flag
Co-authored-by: Samyak Sarnayak <samyak201@gmail.com>
Co-authored-by: Samyak Sarnayak <samyak201@gmail.com>
- formatted analytics_scheduler.py - formatted anomaly_data_view.py - improved logging; switched to error from info incase of errors - removed run_anomaly check from edit-kpi functionality
Import was broken
…respective of whether the run_anomaly status
…kill switch for anomaly
…respective of whether the run_anomaly status
…led without setting anomaly params
feat: count column for druid supports float now
Disable analytics endpoint
The empty prediction dataframe is now given the correct types immediately after creation. This ensures that any data appended to the dataframe will have the correct type. Note: if the columns or the dataframe itself is overwritten, this will not hold and the types may change. Also uses a simpler method to get the last row of the prediction dataframe which prevents loss of types. The earlier version would erase all the metadata and make the dtypes `object`. These 2 changes ensure that the `y` column is always a `float` and the dataframe correctly identifies it as such. Note: the columns can still be overriden by some other code and this cannot be ensured without writing tests.
fix(anomaly): ensure correct data types
fix(docker): add analytics params to alerts worker
These lists are used to populate the filter options in FE. Fixes #1066
…imension-and-subdimensional-options-should-be-searchable
…al-options-should-be-searchable Dimension and subdimensional options should be searchable
…filter fix: check dashboard/datasource active in filter options
…delete called all alerts API when alerts are deleted
fix(anomaly): convert slack into hourly value for hourly KPIs
release: bump version to v0.10.1
|
|
✅ Deploy Preview for frontend-sb ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
manassolanki
approved these changes
Aug 11, 2022
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.
See GitHub release notes (will be added soon) for details