fix: resolve URL path truncation in SSE transport for proxied servers #2412
SOURABHMISHRA5221pull-request-checks.yml
on: pull_request
checks
/
pre-commit
27s
checks
/
readme-snippets
11s
Matrix: checks / test
Annotations
16 warnings and 4 notices
|
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>0t+GVaAAAAAB30STsUFveSbZ+IVIxZySNQlkzRURHRTAyMTkARWRnZQ==
|
|
checks / test (3.12, 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>0ueGVaAAAAAD66oEpTqkKQZXzovoS4xX3QkwyQUEyMDMwMTA3MDM3AEVkZ2U=
|
|
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>0ueGVaAAAAABHDGEmiIMjR5w3Kjlcd2wEUEhYMzFFREdFMDUxNABFZGdl
|
|
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>0uuGVaAAAAACzX33Q+w94RKY8oxos7CZoQlkzRURHRTA0MjEARWRnZQ==
|
|
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>0/uGVaAAAAABnoXJXeCNIRJvTAW/1JgcfQ0gxRURHRTIxMTgARWRnZQ==
|
|
checks / test (3.10, 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>0C+KVaAAAAAD8+xydonzzR7SZ8+ObTL3rQkwyQUEyMDMwMTA3MDMxAEVkZ2U=
|
|
checks / test (3.12, 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>0DOKVaAAAAADoOzCaDiJSQ4TG6srlKXzxQkwyQUEyMDMwMTA1MDUzAEVkZ2U=
|
|
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>0DuKVaAAAAAAM1oFs2o4TS5CBOgCRZ4juQ0gxRURHRTEwMTUARWRnZQ==
|
|
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.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.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
|