fix: resolve URL path truncation in SSE transport for proxied servers #2440
pull-request-checks.yml
on: pull_request
checks
/
pre-commit
22s
checks
/
readme-snippets
10s
Matrix: checks / test
Annotations
1 error, 16 warnings, and 4 notices
checks / pre-commit
Process completed with exit code 1.
|
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>0KiCbaAAAAADj4tO+jSrxRqtBN5MZIfDxQkwyQUEyMDMwMTA2MDMzAEVkZ2U=
|
checks / test (3.10, 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>0KiCbaAAAAADfY1MkF7cbSKcUM38kUn79Q0gxRURHRTIwMTgARWRnZQ==
|
checks / test (3.11, 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>0LyCbaAAAAACXoP4F3FKGT6GWe4GUtatXQkwyQUEyMDMwMTEwMDIzAEVkZ2U=
|
checks / test (3.12, 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>0MSCbaAAAAADCae9EiuImT7s789CedLtsRE0yRURHRTA3MTUARWRnZQ==
|
checks / test (3.13, 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>0YyCbaAAAAACCFrPmWhfkRpGkMupoBGgaQ0hJMzBFREdFMDMwOQBFZGdl
|
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>0bCCbaAAAAABQmesf5JB1S6DoDbNevxTKQkwyQUEyMDMwMTEwMDA3AEVkZ2U=
|
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>0cSCbaAAAAACVQpH2MSbsQLz+QQsisXu1Q0gxRURHRTE4MjEARWRnZQ==
|
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>0fiCbaAAAAAAe34SGiRo1S7HLrgVKtjVVQ0gxRURHRTEyMTIARWRnZQ==
|
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
|