Issue 1356 - Fix SSE unicode line separator handling #2660
pull-request-checks.yml
on: pull_request
checks
/
pre-commit
16s
checks
/
readme-snippets
10s
Matrix: checks / test
Annotations
2 errors, 31 warnings, and 8 notices
checks / pre-commit
Process completed with exit code 1.
|
checks / test (3.10, lowest-direct, windows-latest)
Process completed with exit code 1.
|
checks / test (3.10, 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>0e4jBaAAAAABNcjINaKOhTJk0KsbByFTlQkwyQUEyMDMwMTA4MDUzAEVkZ2U=
|
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>0fIjBaAAAAACP2FWwkCbUTqb+Fqq8Pu3GQkwyQUEyMDMwMTEwMDA1AEVkZ2U=
|
checks / test (3.10, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
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>0e4jBaAAAAAArMEPb3Cv1TLSNh4UO+anKQlkzRURHRTAxMTgARWRnZQ==
|
checks / test (3.12, 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>0fIjBaAAAAAA6P60mThE/SpKopIqMS1G5REVOMzAxMDAwMTA4MDIzAEVkZ2U=
|
checks / test (3.12, 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>0fIjBaAAAAACjtX/5nQSnRp31e1t5SIMIUEhYMzFFREdFMDIxOABFZGdl
|
checks / test (3.13, 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>0fYjBaAAAAABQ6DK96yKjToQC8OfPqcdwUEhYMzFFREdFMDUxMgBFZGdl
|
checks / test (3.13, 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>0fYjBaAAAAAAlHGMqKNzISZwOnprvV5pfREVOMzAxMDAwMTA1MDUzAEVkZ2U=
|
checks / test (3.11, 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>0fojBaAAAAAAL2fJvarwvTaYnNSPSn/LoUEFPRURHRTA2MDkARWRnZQ==
|
checks / test (3.11, highest, ubuntu-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>0pYjBaAAAAAAcMJsc8YrEQra9UBt5hHwQQkwyQUEyMDMwMTEwMDE3AEVkZ2U=
|
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>0rIjBaAAAAACLM4STln/FRLg9BrZT3m67QlkzRURHRTA1MTgARWRnZQ==
|
checks / test (3.12, 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>0r4jBaAAAAABPzKzLsYbAQa5QGyAfiaitREVOMzAxMDAwMTA3MDI5AEVkZ2U=
|
checks / test (3.11, highest, 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>0sojBaAAAAAAqJrUbVuz+QpbHe3Shemz4UEhYMzFFREdFMDYwNwBFZGdl
|
checks / test (3.11, 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>0uIjBaAAAAADFMMATuZcwRqlwH0rSA51yQkwyQUEyMDMwMTEwMDQ1AEVkZ2U=
|
checks / test (3.13, lowest-direct, windows-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>0v4jBaAAAAACnlpjAuk3pQJij7d8Rtn/9Q0hJMzBFREdFMDQxOQBFZGdl
|
checks / test (3.12, 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>0wYjBaAAAAAAFDBGY04zSTZT/af/nF7yrQkwyQUEyMDMwMTA4MDQ1AEVkZ2U=
|
checks / test (3.13, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
|
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, 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.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
|
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.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.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, 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
|