SDK Parity: Avoid Parsing Server Response for non-JsonRPCMessage Requests #2522
pull-request-checks.yml
on: pull_request
checks
/
pre-commit
20s
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, highest, windows-latest)
Process completed with exit code 1.
|
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>0kJaoaAAAAAAhwmkhpsmvQ7ODKPxMUUyvQkwyQUEyMDMwMTA5MDE3AEVkZ2U=
|
checks / test (3.12, highest, 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>0kJaoaAAAAAAxAWGo9wfHQbgqPuMd4BgWQkwyQUEyMDMwMTA3MDA1AEVkZ2U=
|
checks / test (3.12, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
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>0kZaoaAAAAAAQLCXnZ+uhQ5zqGQalHx3BQkwyQUEyMDMwMTA2MDE3AEVkZ2U=
|
checks / test (3.10, highest, 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>0kZaoaAAAAADsyb1jxBjOSp0K8ImjAOt6QkwyQUEyMDMwMTA2MDMzAEVkZ2U=
|
checks / test (3.11, lowest-direct, 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>0kpaoaAAAAAD2srE8elWVTYeyIghBNqLyRE0yRURHRTA4MTAARWRnZQ==
|
checks / test (3.10, lowest-direct, 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>0kpaoaAAAAADeoqOzATq0Tp/NSm7eymKNUEFPRURHRTA1MDcARWRnZQ==
|
checks / test (3.13, 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>0kpaoaAAAAABaa5xHT3XDSaEegKoe/w7wUEFPRURHRTA2MTcARWRnZQ==
|
checks / test (3.11, 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>0k5aoaAAAAABbpUeaBpZIS4SbgqkJzPLmUEhYMzFFREdFMDYwOQBFZGdl
|
checks / test (3.13, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, highest, windows-latest)
Failed to restore: Cache service responded with 400
|
checks / test (3.10, 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>0tpaoaAAAAABn+pLQcURZRpqw1s4am7xJRE0yRURHRTA5MjAARWRnZQ==
|
checks / test (3.10, lowest-direct, 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>0u5aoaAAAAABmRYG7CCDCTLRnfK1a48TUQ0hJMzBFREdFMDQxMABFZGdl
|
checks / test (3.11, 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>0u5aoaAAAAADD0NestK2fQpIpPqC/eIDCUEFPRURHRTA1MTgARWRnZQ==
|
checks / test (3.11, highest, 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>0vJaoaAAAAAAdAshWn7BnSYP0uBhMZtquQkwyQUEyMDMwMTEwMDA3AEVkZ2U=
|
checks / test (3.13, lowest-direct, 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>0vJaoaAAAAAARkja8BordQJYb8uDavg6dUEFPRURHRTA1MTYARWRnZQ==
|
checks / test (3.12, lowest-direct, 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>0wJaoaAAAAAARgeB5AljoT7vG8O/NsFMrUEFPRURHRTA1MTkARWRnZQ==
|
checks / test (3.13, highest, 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>00JaoaAAAAADK00JSx+9GRZdU905OmzeyQkwyQUEyMDMwMTA1MDAzAEVkZ2U=
|
checks / test (3.12, highest, 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.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
|
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.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.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, 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, 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, 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
|