fix: handle ClosedResourceError in StreamableHTTP message router #2709
Triggered via pull request
September 21, 2025 06:14
Edison-A-N
Status
Success
Total duration
2m 55s
Artifacts
–
pull-request-checks.yml
on: pull_request
checks
/
pre-commit
30s
checks
/
readme-snippets
10s
Matrix: checks / test
Annotations
8 errors, 24 warnings, and 8 notices
|
checks / test (3.10, lowest-direct, windows-latest)
Process completed with exit code 1.
|
|
checks / test (3.12, highest, windows-latest)
Process completed with exit code 1.
|
|
checks / test (3.13, lowest-direct, windows-latest)
Process completed with exit code 1.
|
|
checks / test (3.10, highest, windows-latest)
Process completed with exit code 1.
|
|
checks / test (3.11, highest, windows-latest)
Process completed with exit code 1.
|
|
checks / test (3.13, highest, windows-latest)
Process completed with exit code 1.
|
|
checks / test (3.11, lowest-direct, windows-latest)
Process completed with exit code 1.
|
|
checks / test (3.12, lowest-direct, windows-latest)
Process completed with exit code 1.
|
|
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>0/5fPaAAAAADJTbU2TYnXQqcIypniENZ/Q0hJMzBFREdFMDExNQBFZGdl
|
|
checks / test (3.10, 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>0/5fPaAAAAADrGhz6molqSbBjGz1W//NERE0yRURHRTA1MTIARWRnZQ==
|
|
checks / test (3.10, 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>0AJjPaAAAAADNMX8MEO1zSqZRQVcAm0M+UEFPRURHRTA1MDcARWRnZQ==
|
|
checks / test (3.11, 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>0A5jPaAAAAABE1sbOTju/Tr39XN11ZO8+Q0hJMzBFREdFMDMyMABFZGdl
|
|
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>0ApjPaAAAAAAlPoB7/KjSQ5jIip5Y/kK5REVOMzAxMDAwMTA2MDIzAEVkZ2U=
|
|
checks / test (3.11, highest, 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>0BJjPaAAAAAC/bNrO6iWcTI6oFTy5soBdQ0hJMzBFREdFMDQxNQBFZGdl
|
|
checks / test (3.13, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
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>0BJjPaAAAAABfiiuUnZ+CQb6GTlwZofr+QlkzRURHRTA0MTIARWRnZQ==
|
|
checks / test (3.12, 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>0BZjPaAAAAADzZMXEwPjtTI30wrPIUbAnUEhYMzFFREdFMDUxMQBFZGdl
|
|
checks / test (3.13, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.10, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.12, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.13, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.10, highest, 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, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.11, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.12, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
|
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.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.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.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.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, 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.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
|
|
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
|