feat: support progress_callback propagation in ClientSession (issue #1248) #2411
nkaushal99pull-request-checks.yml
on: pull_request
checks
/
pre-commit
26s
checks
/
readme-snippets
11s
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>0GzuVaAAAAAAcTEKOdqHBQIQA1PEHlwiQQ0gxRURHRTE4MTQARWRnZQ==
|
|
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>0HDuVaAAAAAAYOdib8HgUT4vRGheoD/gvQkwyQUEyMDMwMTA1MDE5AEVkZ2U=
|
|
checks / test (3.13, 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>0HDuVaAAAAAC0xHQSTvzqSaFVgUQs+OGuQkwyQUEyMDMwMTA5MDA3AEVkZ2U=
|
|
checks / test (3.10, 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>0HTuVaAAAAACArZCbRp6tSbRlDM9hCy0rUEFPRURHRTA2MDkARWRnZQ==
|
|
checks / test (3.12, 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>0XDuVaAAAAAC5SBI8IWrfS5CZs8SPPbCTQ0gxRURHRTIxMDkARWRnZQ==
|
|
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>0aDuVaAAAAADY9qKUsEAiTJmznz6Rjph4QkwyQUEyMDMwMTA5MDMzAEVkZ2U=
|
|
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>0bTuVaAAAAAB8FAeey5+3Q6sa0Daujua1Q0hHRURHRTE5MDYARWRnZQ==
|
|
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>0cDuVaAAAAAARlczDneBbQbxjoUVasWPAQ0gxRURHRTIzMTIARWRnZQ==
|
|
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
|