Skip to content

Pylint fix

Pylint fix #995

Triggered via push February 12, 2025 18:06
Status Success
Total duration 4m 6s
Artifacts 2

verify.yml

on: push
Ruff check and force
5s
Ruff check and force
Check commit
47s
Check commit
Matrix: prepare-test-cache
Matrix: pytest
Process test coverage
15s
Process test coverage
Run mypy
9s
Run mypy
Process test complexity
5s
Process test complexity
Build and publish Python 🐍 distributions πŸ“¦ to TestPyPI
24s
Build and publish Python 🐍 distributions πŸ“¦ to TestPyPI
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
Prepare
Cache not found for keys: usb-7-Linux-pre-commit-ebcb5e84a5934535c7a308b0ac11e2288e759095ed3ca6167d7919bd9b02e088, usb-7-Linux-pre-commit-
Check commit
Cache not found for keys: usb-7-Linux-pre-commit-ebcb5e84a5934535c7a308b0ac11e2288e759095ed3ca6167d7919bd9b02e088
Create pytest cache for Python 3.11
Cache not found for keys: usb-7-Linux-venv-3.11-73b5c1bd17313957ef6f927a34382cd8b6e8dd2e57924202318778bf4b0be342-eefbf6533dbd50d7eadff6c7b2fae9123d249a5759ed7b2cb50d37b30e28e6c3, usb-7-Linux-venv-3.11-73b5c1bd17313957ef6f927a34382cd8b6e8dd2e57924202318778bf4b0be342-eefbf6533dbd50d7eadff6c7b2fae9123d249a5759ed7b2cb50d37b30e28e6c3, usb-7-Linux-venv-3.11-73b5c1bd17313957ef6f927a34382cd8b6e8dd2e57924202318778bf4b0be342, usb-7-Linux-venv-3.11-
Create pytest cache for Python 3.12
Cache not found for keys: usb-7-Linux-venv-3.12-73b5c1bd17313957ef6f927a34382cd8b6e8dd2e57924202318778bf4b0be342-eefbf6533dbd50d7eadff6c7b2fae9123d249a5759ed7b2cb50d37b30e28e6c3, usb-7-Linux-venv-3.12-73b5c1bd17313957ef6f927a34382cd8b6e8dd2e57924202318778bf4b0be342-eefbf6533dbd50d7eadff6c7b2fae9123d249a5759ed7b2cb50d37b30e28e6c3, usb-7-Linux-venv-3.12-73b5c1bd17313957ef6f927a34382cd8b6e8dd2e57924202318778bf4b0be342, usb-7-Linux-venv-3.12-
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
Build and publish Python 🐍 distributions πŸ“¦ to TestPyPI
Input 'repository_url' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `repository-url` instead.
Build and publish Python 🐍 distributions πŸ“¦ to TestPyPI
Input 'skip_existing' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `skip-existing` instead.
Build and publish Python 🐍 distributions πŸ“¦ to TestPyPI
Input 'repository_url' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `repository-url` instead.
Build and publish Python 🐍 distributions πŸ“¦ to TestPyPI
Input 'skip_existing' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `skip-existing` instead.

Artifacts

Produced during runtime
Name Size Digest
coverage-3.11 Expired
4.89 KB
sha256:2337fc6e94b77c813c1e3b781fa60fbd8634436e0892ec42912602a57ecdaecf
coverage-3.12 Expired
4.9 KB
sha256:8b5d8a2461244921229e3405592208bc26ea957baaefe367ed16e2fdeeb8bf12