fix: handle ClosedResourceError in StreamableHTTP message router #2717
Triggered via pull request
September 23, 2025 00:36
Edison-A-N
Status
Success
Total duration
1m 32s
Artifacts
–
pull-request-checks.yml
on: pull_request
checks
/
pre-commit
25s
checks
/
readme-snippets
13s
Matrix: checks / test
Annotations
1 error, 31 warnings, and 8 notices
|
checks / test (3.10, highest, ubuntu-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>0x+vRaAAAAACd2qDAnEBKSL7WlxtqcTmERE0yRURHRTA0MTMARWRnZQ==
|
|
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 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>0x+vRaAAAAADMCOChLbzSTbv2lj84Ey7WUEFPRURHRTA2MTgARWRnZQ==
|
|
checks / test (3.10, lowest-direct, 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>0yOvRaAAAAADuCwdEC/IYTowhc9YNjgynQkwyQUEyMDMwMTEwMDM5AEVkZ2U=
|
|
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>0yOvRaAAAAACwdixiB6RVSZdQggDkiVWpQlkzRURHRTA0MTAARWRnZQ==
|
|
checks / test (3.12, 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>0yevRaAAAAABOwg05NEmjQ7E/SFRSK+3KREVOMzAxMDAwMTA2MDQ3AEVkZ2U=
|
|
checks / test (3.13, lowest-direct, 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>0yevRaAAAAACOd9Fq9pNJQrNkD0p637exQlkzRURHRTA0MTQARWRnZQ==
|
|
checks / test (3.11, highest, 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>0yuvRaAAAAADJZC2IAZTxRYlhQUrDvT5GQlkzRURHRTA0MTQARWRnZQ==
|
|
checks / test (3.13, highest, ubuntu-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>08uvRaAAAAAC4RfLxUD8aT61pDkUiIqrrQkwyQUEyMDMwMTEwMDM1AEVkZ2U=
|
|
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>09OvRaAAAAAAJUqfyxhTwR46E2Uzx/O6eREVOMzAxMDAwMTA1MDUxAEVkZ2U=
|
|
checks / test (3.10, lowest-direct, 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>09OvRaAAAAAA6Uqg3U/O6QqR6FrICY8otREVOMzAxMDAwMTA2MDQ3AEVkZ2U=
|
|
checks / test (3.13, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.11, 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>09OvRaAAAAADauHj0KZusS6/04f/TaFhnUEFPRURHRTA2MDkARWRnZQ==
|
|
checks / test (3.11, highest, 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>09evRaAAAAACB6feUs0TgQr6sKGh5XEsfREVOMzAxMDAwMTAyMDUxAEVkZ2U=
|
|
checks / test (3.13, highest, windows-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>09uvRaAAAAACtNLW2fsaeQ4jC1bQujb58Q0hJMzBFREdFMDEwNgBFZGdl
|
|
checks / test (3.10, 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>09uvRaAAAAADdRdBkCHPRTbOYU8Kv4zwHUEhYMzFFREdFMDIwNwBFZGdl
|
|
checks / test (3.12, 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>0+evRaAAAAACWrD8rJuf3SYUADcVBH5wbQlkzRURHRTAzMTEARWRnZQ==
|
|
checks / test (3.11, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
|
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, 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, 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, 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, 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
|