error-handling
Error handling guidelines for NeMo-RL. Covers exception specificity, minimal try bodies, and else blocks.
Datos de origen
- Repositorio
- NVIDIA-NeMo/RL
- Última actividad en el origen
- 23 de octubre de 2026 a las 05:20
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 2101
- Forks
- 627
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- error-handling
- description
- Error handling guidelines for NeMo-RL. Covers exception specificity, minimal try bodies, and else blocks.
- when_to_use
- Writing or reviewing exception handling; 'try-except', 'catch all exceptions', 'bare except', 'how to handle errors', during code review.
# Error Handling
## Use Specific Exceptions
When using try-except blocks, limit the except to the smallest set of errors possible.
**Don't:**
```python
try:
open(path, "r").read()
except:
print("Failed to open file")
```
**Do:**
```python
try:
open(path, "r").read()
except FileNotFoundError:
print("Failed to open file")
```
## Fail Loud, Not Silent
When adding a config option or branch, ask: what does the worst plausible misconfiguration do? If it silently
produces *wrong results* rather than an error, add a setup-time `assert`/`raise` so it fails loudly at startup
instead of corrupting a run.
**Examples of silent-wrong worth guarding:**
- An advantage estimator that needs a real `prev_logprobs` while a loss flag zeroes it (advantage degrades to
garbage with no error).
- An agent routed to a teacher alias that has no worker group (cryptic `KeyError` mid-run instead of a
setup-time check).
- A backend/quantization setting silently ignored for a sub-component.
Prefer failing at `setup()` time over a deep-in-the-loop crash; prefer a crash over silent garbage. If you
truly can't validate, surface a logged warning rather than nothing.
Ver en GitHub