[P2] Improve Error Categorization #15
Labels
No labels
audit-2025-12-03
component/api
component/commands
component/llm
component/memory
component/tick-loop
component/tools
priority
high
priority
low
status
in-progress
status
needs-info
status
needs-triage
status
on-hold
type
bug
type
documentation
type
enhancement
type
feature
type
refactor
type
test
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
blightbow/evennia_ai#15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Error handling doesn't distinguish between error types:
Suggested Fix
Implement error classification to enable appropriate handling strategies for each error type.
Priority
P2 — Medium Priority
Source
Architecture Audit 2025-12-03, Priority Recommendations
Implementation complete in commit
5ea5bf953.Changes:
errors.pywithErrorCategoryenum (AUTH, TRANSIENT, BUSINESS_LOGIC, UNKNOWN)classify_http_error(),classify_exception(),should_retry(),should_trip_circuit_breaker()llm/client.pyto use error classification for retry and circuit breaker decisionsKey behavior changes:
Impact: Auth failures no longer cause false service unavailability by tripping the circuit breaker.
Tests: 30 tests added in
test_error_classification.pycovering classification, retry decisions, and LLM client integration.