Spaces:
Running
Running
File size: 1,373 Bytes
026ee5d |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 |
# Error Handling & Logging
This document outlines error handling and logging conventions for DeepCritical.
## Exception Hierarchy
Use custom exception hierarchy (`src/utils/exceptions.py`):
- `DeepCriticalError` (base)
- `SearchError` → `RateLimitError`
- `JudgeError`
- `ConfigurationError`
## Error Handling Rules
- Always chain exceptions: `raise SearchError(...) from e`
- Log errors with context using `structlog`:
```python
logger.error("Operation failed", error=str(e), context=value)
```
- Never silently swallow exceptions
- Provide actionable error messages
## Logging
- Use `structlog` for all logging (NOT `print` or `logging`)
- Import: `import structlog; logger = structlog.get_logger()`
- Log with structured data: `logger.info("event", key=value)`
- Use appropriate levels: DEBUG, INFO, WARNING, ERROR
## Logging Examples
```python
logger.info("Starting search", query=query, tools=[t.name for t in tools])
logger.warning("Search tool failed", tool=tool.name, error=str(result))
logger.error("Assessment failed", error=str(e))
```
## Error Chaining
Always preserve exception context:
```python
try:
result = await api_call()
except httpx.HTTPError as e:
raise SearchError(f"API call failed: {e}") from e
```
## See Also
- [Code Style](code-style.md) - Code style guidelines
- [Testing](testing.md) - Testing guidelines
|