Release 2.7.0 #574
Merged
Release 2.7.0 #574
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
since it is used only by `NumberField`
in which case it will show the grayed-out placeholder "null".
It is now more robust to determine which fields are nullable and which ones are not.
This makes no difference, except avoiding running one unnecessary line of code.
* Add and modify some logging * Cleanup comments and logs * Update azimuth/utils/ml/perturbation_test.py Co-authored-by: Lindsay Brin <lindsay.brin@servicenow.com> --------- Co-authored-by: Lindsay Brin <lindsay.brin@servicenow.com>
* Update python to 3.9 * Resolve TODO * Fix mypy * Update docs --------- Co-authored-by: joseph.marinier <joseph.marinier@servicenow.com>
* Validate positive integers * Change comment into field description * Change thresholds to percentages
on unsuccessful config update
* Modify call to validation module so it uses the task manager and leverage the cache * Reduce batch size in validation module * Rename validation folder * Wait for validation to be done before continuing
Because of what appears to be a bug in FastAPI, our `HTTP_500_INTERNAL_SERVER_ERROR: handle_internal_error` supposed to handle unexpected errors as `{"detail": "Internal server error"}` works for some 500 errors, but not for others. Let's remove it for now, and treat all 500 errors as unexpected, by not showing them to the user.
* Clean up redundant `isort` `args` Remove `args` for `isort` in `.pre-commit-config.yaml` since they are redundant with their definitions in `pyproject.toml`. * Align `isort`'s max line length with `flake8` and `black` * Apply isort
along with a hash of each config to differentiate them easily.
so we are not tempted to call them on the objects (for example with autocomplete in PyCharm)
* Clean up `by_alias` for config which had no effect since the config doesn't have aliases. * Clean up `AliasModel`'s `dict()` and `no_alias_dict()` methods * Fix perturbation testing summary now that it has snake_case column headers like our other CSV files. * Fix test
* Clean up unused `datasetInfo.classNames` * Clean up `datasetInfo` - Replace `datasetInfo.evalClassDistribution` and `datasetInfo.trainClassDistribution` with `datasetInfo.utteranceCountPerDatasetSplit` * Clean up `object_loader.py` * Handle more `AzimuthValidationError`s when loading a `CustomObject` instead of unexpected internal server errors. * Fix nullable `StringField` * Fix dataset columns repeated labels * Reuse `handleDiscard()` * Render config modal only if it is open (optimization) * Expand the Project Configuration accordion by default * Support null dataset * Open config modal if dataset is null * Add front-end validation in config for empty strings and numbers out of range. * Log changes * Clean up getting varnames from classes' `__init__()` * Keep toasts for 10 seconds instead of 5
Co-authored-by: joseph.marinier <joseph.marinier@servicenow.com>
Bumps [pymdown-extensions](https://github.com/facelessuser/pymdown-extensions) from 9.3 to 10.0. - [Release notes](https://github.com/facelessuser/pymdown-extensions/releases) - [Commits](facelessuser/pymdown-extensions@9.3...10.0) --- updated-dependencies: - dependency-name: pymdown-extensions dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Create reusable component `CustomObjectFields` * Fix pages assuming config is loaded * Memoize `resultingConfig` since a `useEffect` depends on it * Support custom metrics
* Add a make target to serve docs * Small fixes and enhancements * Document launching Azimuth with or without a config file * Release 2.6.2 * Try `setup-poetry@v8` * Fix exporting `CFG_PATH`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.