Expand description
Server error types and HTTP response handling
This module provides a unified error handling system for the Actix-web server. All errors are converted to HTTP responses with appropriate status codes.
§Error Types
BadRequest: Client errors (400)ToolNotFound: Tool not available (404)ToolExecutionError: Tool execution failed (400)ToolApprovalRequired: Tool needs user approval (403)NotFound: Resource not found (404)ProxyAuthRequired: Proxy authentication needed (428)InternalError: Server errors (500)StorageError: File system errors (500)SerializationError: JSON serialization errors (500)
Enums§
- AppError
- Application error enum with HTTP status code mapping
Functions§
- error_
value - The value of the
"error"key in bamboo’s canonical error envelope ({"error": {"message", "type", "code"}}, matchingAppError’sResponseError::error_responsebody) — for the minority of handlers that are not (yet) modeled as anAppErrorvariant but still need to return extra sibling fields alongside the error (e.g.session_id,message_id) that a bareAppErrorhas no place for. - json_
error - Build bamboo’s canonical JSON error response for code paths that cannot
return an
AppErrordirectly (most notably middleware and handlers that must preserve extra response headers). - json_
internal_ server_ error - Preserve an existing
actix_web::Resultsignature while ensuring the framework error is rendered with bamboo’s canonical JSON envelope instead of Actix’s defaulttext/plainconvenience-error body.
Type Aliases§
- Result
- Result type alias for server operations