feat: support progress_callback propagation in ClientSession (issue #1248) #2721
pull-request-checks.yml
on: pull_request
checks
/
pre-commit
30s
checks
/
readme-snippets
10s
Matrix: checks / test
Annotations
1 error, 31 warnings, and 8 notices
checks / test (3.11, highest, windows-latest)
Process completed with exit code 1.
|
checks / test (3.12, lowest-direct, 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>0SYrSaAAAAAB8S8autWGqSapFq+eJVW5+QkwyQUEyMDMwMTEwMDE5AEVkZ2U=
|
checks / test (3.12, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, highest, 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>0SorSaAAAAAD073x4JvbhRr+ax1ow28VfQ0hJMzBFREdFMDExOABFZGdl
|
checks / test (3.10, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, lowest-direct, 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>0SorSaAAAAADvJdsqvxYMQKlowk7qXbQ8QkwyQUEyMDMwMTEwMDIzAEVkZ2U=
|
checks / test (3.10, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, highest, 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>0S4rSaAAAAAC1HWI85zU0Sr15qfI4CF4bQ0hJMzBFREdFMDEwNgBFZGdl
|
checks / test (3.13, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.11, lowest-direct, 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>0SorSaAAAAACbJFN6hOoiRaB/hv2K/nktQ0hJMzBFREdFMDEwOABFZGdl
|
checks / test (3.11, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, lowest-direct, 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>0TIrSaAAAAABRbvPIcsznTIHdPKGaTxVzRE0yRURHRTA0MjAARWRnZQ==
|
checks / test (3.13, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.12, highest, 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>0S4rSaAAAAADJ6ZCn8eSZRYw826kRDnOmQlkzRURHRTAxMTUARWRnZQ==
|
checks / test (3.12, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.11, highest, 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>0S4rSaAAAAADutZsn4Nt6SYr66ZIri0qiUEFPRURHRTA2MTQARWRnZQ==
|
checks / test (3.11, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, highest, 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>0cIrSaAAAAACzZ0DtayUATIdnNQ5yl+6QQkwyQUEyMDMwMTEwMDExAEVkZ2U=
|
checks / test (3.10, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.12, highest, 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>0eorSaAAAAAB8MTO6glTVR4Y5VQhoSPz+UEFPRURHRTA1MTMARWRnZQ==
|
checks / test (3.12, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, lowest-direct, 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>0hYrSaAAAAABW/YA9K2ebQLo77kmREsp2QkwyQUEyMDMwMTA4MDM5AEVkZ2U=
|
checks / test (3.10, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, highest, 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>0h4rSaAAAAABnpRuoIclKSrga6Eh6rXFoQ0hJMzBFREdFMDMyMgBFZGdl
|
checks / test (3.13, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.12, lowest-direct, 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>0i4rSaAAAAABnsVoCbuHLTYBdB+1qPId4QkwyQUEyMDMwMTA5MDA5AEVkZ2U=
|
checks / test (3.12, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.11, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.13, lowest-direct, 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>0lIrSaAAAAABndt73FQu9RqrAksgXDSNXREVOMzAxMDAwMTAxMDM5AEVkZ2U=
|
checks / test (3.13, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.11, lowest-direct, 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>0oYrSaAAAAAD937sz2WLvT5x0A1XqyyD0QlkzRURHRTA0MjAARWRnZQ==
|
checks / test (3.11, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, highest, 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, highest, 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.10, lowest-direct, 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, highest, 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, lowest-direct, 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, highest, 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, lowest-direct, 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, lowest-direct, 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
|