Add pyright strict mode on the whole project (#1254) #381
main-checks.yml
on: push
checks
/
pre-commit
28s
checks
/
readme-snippets
13s
Matrix: checks / test
Annotations
16 warnings and 4 notices
checks / test (3.11, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0FC+aaAAAAACeUVH7bNogRqTxyW1JTZ/OQkwyQUEyMDMwMTA5MDM5AEVkZ2U=
|
checks / test (3.11, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0GC+aaAAAAAARNmRturP/TZSCtq48WynmQkwyQUEyMDMwMTA4MDA1AEVkZ2U=
|
checks / test (3.13, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.12, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0GS+aaAAAAACL5cIj0qHbTp77C3Ls3ThUUEhYMzFFREdFMDUxMQBFZGdl
|
checks / test (3.12, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Gy+aaAAAAAAgl6l5ke4YTpaGCe8Xp8/ORE0yRURHRTA5MTMARWRnZQ==
|
checks / test (3.10, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Vy+aaAAAAADQSSMA8QkfRLhLEvN5kgjxQlkzRURHRTA0MTAARWRnZQ==
|
checks / test (3.10, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.11, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0XS+aaAAAAAB0NMlv8H1+TLdyvO/O+KrAQkwyQUEyMDMwMTA5MDMxAEVkZ2U=
|
checks / test (3.11, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0XS+aaAAAAAB3ysfDpmiVS59l1okxk1o+QkwyQUEyMDMwMTA4MDI3AEVkZ2U=
|
checks / test (3.13, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.12, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0YC+aaAAAAABpH02qPjcZTZ8cgc4UIHaRQ0gxRURHRTIyMDgARWRnZQ==
|
checks / test (3.12, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, windows-latest)
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
|
checks / test (3.11, windows-latest)
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
|
checks / test (3.13, windows-latest)
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
|
checks / test (3.12, windows-latest)
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
|