fix: prevent async generator cleanup errors in StreamableHTTP transport #2454
mous222pull-request-checks.yml
on: pull_request
checks
/
pre-commit
26s
checks
/
readme-snippets
10s
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>0mBOdaAAAAADSEDXMECS8TKRRBdSPiUicQkwyQUEyMDMwMTA3MDMzAEVkZ2U=
|
|
checks / test (3.11, 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>0mxOdaAAAAAAlDsN7FfzWRIj2m7Xw7MTsRE0yRURHRTA3MTgARWRnZQ==
|
|
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>0nROdaAAAAAAXTJaFWHzrQZ8mSwo5cxUYQkwyQUEyMDMwMTEwMDAzAEVkZ2U=
|
|
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>0nBOdaAAAAACFGvuFhMkoQIv2qoXueBGpQkwyQUEyMDMwMTA1MDA3AEVkZ2U=
|
|
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>01BOdaAAAAAA+8UTCdsXjQZiMzU2SEyQxUEFPRURHRTA1MTcARWRnZQ==
|
|
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>03xOdaAAAAAAmxhu90UEmTqTnd+zONLzdQkwyQUEyMDMwMTA1MDM1AEVkZ2U=
|
|
checks / test (3.11, 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>04xOdaAAAAAAzqmbhmbwFTbvaVJmgU6J2QkwyQUEyMDMwMTA3MDI3AEVkZ2U=
|
|
checks / test (3.12, 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>06ROdaAAAAACzJYedXO6kTJ3i1uKJhuEQRE0yRURHRTA5MTkARWRnZQ==
|
|
checks / test (3.13, 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.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.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
|