fix: resolve URL path truncation in SSE transport for proxied servers #2441
SOURABHMISHRA5221pull-request-checks.yml
on: pull_request
checks
/
pre-commit
29s
checks
/
readme-snippets
13s
Matrix: checks / test
Annotations
3 errors, 15 warnings, and 4 notices
|
checks / pre-commit
Process completed with exit code 1.
|
|
checks / test (3.10, windows-latest)
Process completed with exit code 1.
|
|
checks / test (3.10, windows-latest)
Event loop is closed
|
|
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>0MCGbaAAAAAAcYXJicrdvSrWxcZXeecJ+QkwyQUEyMDMwMTA0MDM1AEVkZ2U=
|
|
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>0MiGbaAAAAAAEYhLEKRYOR7pfC3w9eeLlQ0gxRURHRTIwMTUARWRnZQ==
|
|
checks / test (3.11, 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>0MyGbaAAAAADPIk+mab3fTq/AwYYh5D33RE0yRURHRTA4MTUARWRnZQ==
|
|
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>0MiGbaAAAAAC2gFgmLwNcQ7SrdpEPYsdlQlkzRURHRTA0MTEARWRnZQ==
|
|
checks / test (3.12, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
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>0dyGbaAAAAAAOE2YR+ZnyTYkq//SOEP3qQ0gxRURHRTE4MDYARWRnZQ==
|
|
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>0fSGbaAAAAAADIyJx16UeRaO18YhGpzTvRE0yRURHRTA3MTkARWRnZQ==
|
|
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>0fSGbaAAAAAD88xkBcShlS7TEAilLe5vzUEFPRURHRTA1MDgARWRnZQ==
|
|
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
|