refactor: rename custom_headers to headers in internall calls #1298
TymekAnnotations
62 errors and 7 warnings
|
main
Process completed with exit code 2.
|
|
tox (macos-latest, 3.8)
[notice] A new release of pip is available: 21.1.1 -> 25.0
[notice] To update, run: python3.8 -m pip install --upgrade pip
|
|
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.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)
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.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.12)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.12)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.12)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.12)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.12)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.12)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.12)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.12)
cannot schedule new futures after shutdown
|
|
tox (windows-latest, 3.12)
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
|
|
main
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
tox (ubuntu-latest, 3.10)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
tox (ubuntu-latest, 3.9)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
tox (ubuntu-latest, 3.11)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
tox (ubuntu-latest, 3.8)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
tox (ubuntu-latest, 3.13)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
tox (ubuntu-latest, 3.12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|