Skip to content

fix: linting

fix: linting #1689

Triggered via push September 12, 2025 09:19
Status Success
Total duration 4m 48s
Artifacts

pull_request.yml

on: push
Matrix: tox
Fit to window
Zoom out
Zoom in

Annotations

52 errors and 6 notices
tox (macos-latest, 3.8)
[notice] A new release of pip is available: 21.1.1 -> 25.0.1 [notice] To update, run: python3.8 -m pip install --upgrade pip
tox (windows-latest, 3.9)
cannot schedule new futures after shutdown
tox (windows-latest, 3.9)
cannot schedule new futures after shutdown
tox (windows-latest, 3.9)
cannot schedule new futures after shutdown
tox (windows-latest, 3.9)
cannot schedule new futures after shutdown
tox (windows-latest, 3.9)
cannot schedule new futures after shutdown
tox (windows-latest, 3.9)
cannot schedule new futures after shutdown
tox (windows-latest, 3.9)
cannot schedule new futures after shutdown
tox (windows-latest, 3.9)
cannot schedule new futures after shutdown
tox (windows-latest, 3.9)
cannot schedule new futures after shutdown
tox (windows-latest, 3.9)
cannot schedule new futures after shutdown
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
tox (windows-latest, 3.13)
cannot schedule new futures after shutdown
tox (windows-latest, 3.11)
cannot schedule new futures after shutdown
tox (windows-latest, 3.11)
cannot schedule new futures after shutdown
tox (windows-latest, 3.11)
cannot schedule new futures after shutdown
tox (windows-latest, 3.11)
cannot schedule new futures after shutdown
tox (windows-latest, 3.11)
cannot schedule new futures after shutdown
tox (windows-latest, 3.11)
cannot schedule new futures after shutdown
tox (windows-latest, 3.11)
cannot schedule new futures after shutdown
tox (windows-latest, 3.11)
cannot schedule new futures after shutdown
tox (windows-latest, 3.11)
cannot schedule new futures after shutdown
tox (windows-latest, 3.11)
cannot schedule new futures after shutdown
tox (windows-latest, 3.10)
cannot schedule new futures after shutdown
tox (windows-latest, 3.10)
cannot schedule new futures after shutdown
tox (windows-latest, 3.10)
cannot schedule new futures after shutdown
tox (windows-latest, 3.10)
cannot schedule new futures after shutdown
tox (windows-latest, 3.10)
cannot schedule new futures after shutdown
tox (windows-latest, 3.10)
cannot schedule new futures after shutdown
tox (windows-latest, 3.10)
cannot schedule new futures after shutdown
tox (windows-latest, 3.10)
cannot schedule new futures after shutdown
tox (windows-latest, 3.10)
cannot schedule new futures after shutdown
tox (windows-latest, 3.10)
cannot schedule new futures after shutdown
tox (windows-latest, 3.12)
cannot schedule new futures after shutdown
tox (windows-latest, 3.8)
cannot schedule new futures after shutdown
tox (windows-latest, 3.8)
cannot schedule new futures after shutdown
tox (windows-latest, 3.8)
cannot schedule new futures after shutdown
tox (windows-latest, 3.8)
cannot schedule new futures after shutdown
tox (windows-latest, 3.8)
cannot schedule new futures after shutdown
tox (windows-latest, 3.8)
cannot schedule new futures after shutdown
tox (windows-latest, 3.8)
cannot schedule new futures after shutdown
tox (windows-latest, 3.8)
cannot schedule new futures after shutdown
tox (windows-latest, 3.8)
cannot schedule new futures after shutdown
tox (windows-latest, 3.8)
cannot schedule new futures after shutdown
tox (windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
tox (windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
tox (windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
tox (windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
tox (windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
tox (windows-latest, 3.8)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677