Skip to content

fix: update response status code for invalid session ID in HTTPSessionManger #2737

fix: update response status code for invalid session ID in HTTPSessionManger

fix: update response status code for invalid session ID in HTTPSessionManger #2737

Triggered via pull request September 24, 2025 13:27
Status Success
Total duration 2m 12s
Artifacts

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
30s
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>05/HTaAAAAAC64iSramGiS5iEQQQDvpD8QkwyQUEyMDMwMTEwMDUxAEVkZ2U=
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>06PHTaAAAAAANPE3I6F/sQ7CmFg97HGtTQkwyQUEyMDMwMTA4MDUxAEVkZ2U=
checks / test (3.11, 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>06PHTaAAAAACPtHVKUz39QJkf6w+9fCJmQkwyQUEyMDMwMTEwMDI5AEVkZ2U=
checks / test (3.12, highest, 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>06fHTaAAAAACesos4rwP8TYSv7iUeHYrGQ0hJMzBFREdFMDEyMQBFZGdl
checks / test (3.10, 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>06vHTaAAAAAC5x59+J+7KT4X+Rlzap6CsQ0hJMzBFREdFMDExMABFZGdl
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>06fHTaAAAAAAlIUXEW3bdRpNNmY1N6FW6QkwyQUEyMDMwMTEwMDQ1AEVkZ2U=
checks / test (3.13, 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>06vHTaAAAAAADP+xYRDarRp0x3hZyW2TGQ0hJMzBFREdFMDQxMQBFZGdl
checks / test (3.10, 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>06fHTaAAAAACDksVO5vpiSIiK21+kZe2PQlkzRURHRTAzMDcARWRnZQ==
checks / test (3.11, lowest-direct, ubuntu-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>0EfLTaAAAAAASf0VI1EKLS5rmWPa2M0xIREVOMzAxMDAwMTA4MDMzAEVkZ2U=
checks / test (3.13, lowest-direct, windows-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>0GfLTaAAAAAB8ZoTlyDNoToD1y11/vcC/QkwyQUEyMDMwMTEwMDA1AEVkZ2U=
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>0G/LTaAAAAAAEQ8nqclM4S7kUJo1c8wbWREVOMzAxMDAwMTA3MDQ5AEVkZ2U=
checks / test (3.12, 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>0I/LTaAAAAACxSiMNVnTARZhrQe8UpOeoUEhYMzFFREdFMDUxNQBFZGdl
checks / test (3.12, 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>0KfLTaAAAAACKi9osz5mFRKPO4EWuOUTZQlkzRURHRTAzMTEARWRnZQ==
checks / test (3.11, 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>0K/LTaAAAAABrRWxu5khZRLNZhPl3lFb1UEFPRURHRTA2MjAARWRnZQ==
checks / test (3.13, 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>0MPLTaAAAAAD/iKSF1p6kR6yEftjlmAfMQlkzRURHRTAxMTEARWRnZQ==
checks / test (3.11, lowest-direct, 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>0RfLTaAAAAABS7Y3MPBhnSoih2X0mpGGhREVOMzAxMDAwMTAxMDE5AEVkZ2U=
checks / test (3.10, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
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.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.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, 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.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.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