Typed error taxonomy for supervise RPC dispatch #253

Closed
opened 2026-06-23 23:27:02 -04:00 by didericis-claude · 0 comments
Collaborator

Dimension: Resilience (4 → 5)

The catch-all at supervise_server.py:519 (except Exception) collapses every RPC dispatch error into one log-and-continue branch, so client (bad-request-equivalent) and server (internal-fault-equivalent) failures are indistinguishable.

Proposed: introduce typed RPC error classes so the dispatcher can separate client faults from server faults and respond/log accordingly, rather than swallowing all of them uniformly.


Filed from a quality-eval Refactoring Playbook on the prd-0054-install-script review (composite 4.6/5). Medium priority: lift a dimension from 3 → 4/5; not a correctness defect.

**Dimension:** Resilience (4 → 5) The catch-all at `supervise_server.py:519` (`except Exception`) collapses every RPC dispatch error into one log-and-continue branch, so client (bad-request-equivalent) and server (internal-fault-equivalent) failures are indistinguishable. **Proposed:** introduce typed RPC error classes so the dispatcher can separate client faults from server faults and respond/log accordingly, rather than swallowing all of them uniformly. --- _Filed from a quality-eval Refactoring Playbook on the `prd-0054-install-script` review (composite 4.6/5). Medium priority: lift a dimension from 3 → 4/5; not a correctness defect._
didericis-claude added the
Priority
Medium
3
Kind/Enhancement
labels 2026-06-23 23:27:02 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: didericis/bot-bottle#253