Skip to content

Fix httpstreamable errorcode #2392

Fix httpstreamable errorcode

Fix httpstreamable errorcode #2392

Triggered via pull request August 5, 2025 20:49
Status Success
Total duration 2m 26s
Artifacts

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
29s
checks / pre-commit
checks  /  readme-snippets
9s
checks / readme-snippets
Matrix: checks / test
Fit to window
Zoom out
Zoom in

Annotations

16 warnings and 4 notices
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>0n26SaAAAAAC9oXJIoX9DSKbyDGORfrpzRE0yRURHRTA5MDkARWRnZQ==
checks / test (3.10, 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>0oW6SaAAAAADTmTyIomO8RprGIKcpl0n0QkwyQUEyMDMwMTEwMDQ3AEVkZ2U=
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>0oW6SaAAAAAAvv+OZjzswS7TxnOjGP30+UEFPRURHRTA1MDgARWRnZQ==
checks / test (3.12, ubuntu-latest)
Failed to restore: Cache service responded with 400
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>0oW6SaAAAAABEJ+Jpl9u0QKYpZDmESxxWQlkzRURHRTAzMDkARWRnZQ==
checks / test (3.11, 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>02W6SaAAAAACvaG3zrOO7Q5MRcM2ClBeARE0yRURHRTEwMDcARWRnZQ==
checks / test (3.10, 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>0526SaAAAAAAHLMauoCwUQYC/MaP80CU4QkwyQUEyMDMwMTA4MDAzAEVkZ2U=
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>0626SaAAAAABPgFMpi34KR5RJz4EKAuTeQ0hJMzBFREdFMDExMgBFZGdl
checks / test (3.12, 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>07W6SaAAAAAA2dSW2D0MWTrJLmYA1eh6iQlkzRURHRTAyMTIARWRnZQ==
checks / test (3.11, 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.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
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