Skip to content

SDK Parity: Avoid Parsing Server Response for non-JsonRPCMessage Requests #2523

SDK Parity: Avoid Parsing Server Response for non-JsonRPCMessage Requests

SDK Parity: Avoid Parsing Server Response for non-JsonRPCMessage Requests #2523

Triggered via pull request August 22, 2025 16:12
Status Success
Total duration 1m 30s
Artifacts

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
26s
checks / pre-commit
checks  /  readme-snippets
11s
checks / readme-snippets
Matrix: checks / test
Fit to window
Zoom out
Zoom in

Annotations

32 warnings and 8 notices
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>0JZeoaAAAAADBRWmrrIFFRb8CQvoWGprJQkwyQUEyMDMwMTEwMDA5AEVkZ2U=
checks / test (3.12, 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>0JpeoaAAAAAAhSONjw8ZCTrfKjqokKGenQkwyQUEyMDMwMTA1MDIxAEVkZ2U=
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>0JpeoaAAAAAARSmZr9+m0RaXt5V1qMOiLRE0yRURHRTA4MTkARWRnZQ==
checks / test (3.13, highest, 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>0KZeoaAAAAAAxz/orNE9WTIs9fNl5pfmFQ0gxRURHRTIyMTYARWRnZQ==
checks / test (3.12, 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>0KZeoaAAAAAArt/hFOBu9Sad2NfpeV3OpQkwyQUEyMDMwMTA1MDExAEVkZ2U=
checks / test (3.11, 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>0KJeoaAAAAACyZVnbvP+iT6PrPgga074MUEhYMzFFREdFMDIxNQBFZGdl
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>0KJeoaAAAAAB29c6HUsCZRbUBXubNUe0sUEFPRURHRTA1MTIARWRnZQ==
checks / test (3.13, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
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>0K5eoaAAAAAA3EUkHrHc/TIv+sxc9GkbJUEFPRURHRTA2MDkARWRnZQ==
checks / test (3.10, lowest-direct, 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>0SpeoaAAAAAAFnED5/V3TTKHSZ3fpjgqyQ0gxRURHRTA5MDgARWRnZQ==
checks / test (3.10, highest, 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>0TZeoaAAAAABxAYHvTbOvRrS+feEX6kGnUEhYMzFFREdFMDIxNgBFZGdl
checks / test (3.11, 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>0T5eoaAAAAADegHOp8ExNQYXVfOtQKu/zQkwyQUEyMDMwMTA1MDAzAEVkZ2U=
checks / test (3.12, 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>0UZeoaAAAAADWSxDn7XO/TJYJWhpv0fy2UEFPRURHRTA2MTUARWRnZQ==
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>0UpeoaAAAAAA0rvIf+YiLSowsU6sCbP9IQ0gxRURHRTIwMDkARWRnZQ==
checks / test (3.13, 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>0U5eoaAAAAAA8DWDbYnVjSrsiSbzRCdq7QlkzRURHRTA0MTgARWRnZQ==
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 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>0WZeoaAAAAAAUpVjOYMzaQ5C9ogdw5MuLQkwyQUEyMDMwMTA4MDE3AEVkZ2U=
checks / test (3.10, 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>0WpeoaAAAAABDevqIdmSVQYmOZXPMfZm2UEFPRURHRTA2MTUARWRnZQ==
checks / test (3.12, 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.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.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.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.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
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