Skip to content

Handles message type Exception in lowlevel/server.py _handle_message function. Mentioned as TODO on line 528. #2790

Handles message type Exception in lowlevel/server.py _handle_message function. Mentioned as TODO on line 528.

Handles message type Exception in lowlevel/server.py _handle_message function. Mentioned as TODO on line 528. #2790

Triggered via pull request September 30, 2025 13:13
Status Success
Total duration 1m 53s
Artifacts

pull-request-checks.yml

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

Annotations

16 errors and 16 warnings
checks / test (3.12, lowest-direct, ubuntu-latest)
Process completed with exit code 1.
checks / test (3.10, highest, ubuntu-latest)
Process completed with exit code 1.
checks / test (3.13, highest, ubuntu-latest)
Process completed with exit code 1.
checks / test (3.11, highest, ubuntu-latest)
Process completed with exit code 1.
checks / test (3.10, lowest-direct, ubuntu-latest)
Process completed with exit code 1.
checks / test (3.11, lowest-direct, ubuntu-latest)
Process completed with exit code 1.
checks / test (3.12, highest, ubuntu-latest)
Process completed with exit code 1.
checks / test (3.13, lowest-direct, ubuntu-latest)
Process completed with exit code 1.
checks / test (3.12, highest, windows-latest)
Process completed with exit code 1.
checks / test (3.11, highest, windows-latest)
Process completed with exit code 1.
checks / test (3.13, lowest-direct, windows-latest)
Process completed with exit code 1.
checks / test (3.12, lowest-direct, windows-latest)
Process completed with exit code 1.
checks / test (3.10, lowest-direct, windows-latest)
Process completed with exit code 1.
checks / test (3.11, lowest-direct, windows-latest)
Process completed with exit code 1.
checks / test (3.13, highest, windows-latest)
Process completed with exit code 1.
checks / test (3.10, highest, windows-latest)
Process completed with exit code 1.
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 restore: Cache service responded with 400
checks / test (3.13, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.11, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
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 restore: Cache service responded with 400
checks / test (3.12, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, highest, windows-latest)
Failed to restore: Cache service responded with 400
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 restore: Cache service responded with 400
checks / test (3.12, lowest-direct, 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.11, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, highest, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, highest, windows-latest)
Failed to restore: Cache service responded with 400