-
Notifications
You must be signed in to change notification settings - Fork 0
Bump joblib from 1.1.0 to 1.2.0 #39
base: main
Are you sure you want to change the base?
Conversation
Bumps [joblib](https://github.com/joblib/joblib) from 1.1.0 to 1.2.0. - [Release notes](https://github.com/joblib/joblib/releases) - [Changelog](https://github.com/joblib/joblib/blob/master/CHANGES.rst) - [Commits](joblib/joblib@1.1.0...1.2.0) --- updated-dependencies: - dependency-name: joblib dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Terraform Format and Style 🖌
|
ML Lint output:ML Project Report
ReportsVersion Control (
|
Passed | Score | Weight | Rule | Slug |
---|---|---|---|---|
✅ | 100.0% | 1 | Project uses Git | version-control/code/git |
✅ | 100.0% | 1 | Project should not have any large files in its Git history | version-control/code/git-no-big-files |
✅ | 100.0% | 1 | DVC: Project uses Data Version Control | version-control/data/dvc |
❌ | 0.0% | 1 | DVC: Is installed | version-control/data/dvc-is-installed |
✅ | 100.0% | 1 | DVC: Folder '.dvc' should be committed to Git | version-control/data/commit-dvc-folder |
❌ | 0.0% | 1 | DVC: Should have at least one remote data storage configured | version-control/data/dvc-has-remote |
❌ | 0.0% | 1 | DVC: Should be tracking at least one data file | version-control/data/dvc-has-files |
Total | ||||
❌ | 57.1% | Version Control | version-control |
Dependency Management (dependency-management
) — 100.0%
Passed | Score | Weight | Rule | Slug |
---|---|---|---|---|
✅ | 100.0% | 1 | Project properly keeps track of its dependencies | dependency-management/use |
✅ | 100.0% | 1 | Project should only use one dependency manager | dependency-management/single |
✅ | 100.0% | 1 | Project places its development dependencies in dev-dependencies | dependency-management/use-dev |
Total | ||||
✅ | 100.0% | Dependency Management | dependency-management |
Code Quality (code-quality
) — 52.0%
Passed | Score | Weight | Rule | Slug |
---|---|---|---|---|
❌ | 20.0% | 1 | Project should use code quality linters | code-quality/use-linters |
❌ | 40.0% | 1 | All code quality linters should be installed in the current environment | code-quality/linters-installed |
✅ | 100.0% | 1 | Pylint reports no issues with this project | code-quality/pylint/no-issues |
✅ | 100.0% | 1 | Pylint is configured for this project | code-quality/pylint/is-configured |
❌ | 0.0% | 1 | isort reports no issues with this project | code-quality/isort/no-issues |
❌ | 0.0% | 0 | isort is properly configured | code-quality/isort/is-configured |
Total | ||||
❌ | 52.0% | Code Quality | code-quality |
Details — Project should use code quality linters — ❌
Linters detected:
- Pylint
However, these linters were missing from your project:
- Mypy
- Black
- isort
- Bandit
We recommend that you start using these linters in your project to help you measure and maintain the quality of your code.
This rule will be satisfied, iff for each of these linters:
- Either there is a configuration file for this linter in the project
- Or the linter is a dependency of the project
Specifically, we recommend adding each linter to the development dependencies of your dependency manager,
e.g. using poetry add --dev mypy
or pipenv install --dev mypy
Details — All code quality linters should be installed in the current environment — ❌
The following linters were not installed, so we could not analyse what they had to say about your project:
- Mypy
- Black
- Bandit
Details — Pylint reports no issues with this project — ✅
Congratulations, Pylint is happy with your project!
Details — isort reports no issues with this project — ❌
isort reported 7 files in your project that it would fix:
notifications/telegram.py
- Imports are incorrectly sorted and/or formatted.src/train_model.py
- Imports are incorrectly sorted and/or formatted.src/inference.py
- Imports are incorrectly sorted and/or formatted.src/frontend/app.py
- Imports are incorrectly sorted and/or formatted.src/tests/test_preprocess.py
- Imports are incorrectly sorted and/or formatted.src/common/preprocessing.py
- Imports are incorrectly sorted and/or formatted.src/alertmetrics/app.py
- Imports are incorrectly sorted and/or formatted.
isort can fix these issues automatically when you run isort .
in your project.
Details — isort is properly configured — ❌
isort is not properly configured.
In order to be compatible with Black, which mllint also recommends using,
you should configure isort
to use the black
profile.
Furthermore, we recommend centralising your configuration in your pyproject.toml
Thus, ensure that your pyproject.toml
contains at least the following section:
[tool.isort]
profile = "black"
Testing (testing
) — 11.4%
Passed | Score | Weight | Rule | Slug |
---|---|---|---|---|
❌ | 45.5% | 1 | Project has automated tests | testing/has-tests |
❌ | 0.0% | 1 | Project passes all of its automated tests | testing/pass |
❌ | 0.0% | 1 | Project provides a test coverage report | testing/coverage |
❌ | 0.0% | 1 | Tests should be placed in the tests folder | testing/tests-folder |
Total | ||||
❌ | 11.4% | Testing | testing |
Details — Project has automated tests — ❌
There is 1 test file in your project, which meets the minimum of 1 test file required.
However, this only equates to 9.090909% of Python files in your project being tests, while mllint
expects that 20% of your project's Python files are tests.
Details — Project passes all of its automated tests — ❌
No test report was provided.
Please update the testing.report
setting in your project's mllint
configuration to specify the path to your project's test report.
When using pytest
to run your project's tests, use the --junitxml=<filename>
option to generate such a test report, e.g.:
pytest --junitxml=tests-report.xml
Details — Project provides a test coverage report — ❌
No test coverage report was provided.
Please update the testing.coverage.report
setting in your project's mllint
configuration to specify the path to your project's test coverage report.
Generating a test coverage report with pytest
can be done by adding and installing pytest-cov
as a development dependency of your project. Then use the following command to run your tests and generate both a test report as well as a coverage report:
pytest --junitxml=tests-report.xml --cov=path_to_package_under_test --cov-report=xml
Details — Tests should be placed in the tests folder — ❌
The following test files have been detected that are not in the tests
folder at the root of your project:
- /home/runner/work/nidhogg/nidhogg/src/tests/test_preprocess.py
Continuous Integration (ci
) — 100.0%
Passed | Score | Weight | Rule | Slug |
---|---|---|---|---|
✅ | 100.0% | 1 | Project uses Continuous Integration (CI) | ci/use |
Total | ||||
✅ | 100.0% | Continuous Integration | ci |
Bumps joblib from 1.1.0 to 1.2.0.
Changelog
Sourced from joblib's changelog.
Commits
5991350
Release 1.2.03fa2188
MAINT cleanup numpy warnings related to np.matrix in tests (#1340)cea26ff
CI test the future loky-3.3.0 branch (#1338)8aca6f4
MAINT: remove pytest.warns(None) warnings in pytest 7 (#1264)067ed4f
XFAIL test_child_raises_parent_exits_cleanly with multiprocessing (#1339)ac4ebd5
MAINT add back pytest warnings plugin (#1337)a23427d
Test child raises parent exits cleanly more reliable on macos (#1335)ac09691
[MAINT] various test updates (#1334)4a314b1
Vendor loky 3.2.0 (#1333)bdf47e9
Make test_parallel_with_interactively_defined_functions_default_backend timeo...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and languageYou can disable automated security fix PRs for this repo from the Security Alerts page.