docs: a pod over the namespace quota fails its execution
Merged
HA
5d ago+1+1+0123456789-1-1-0123456789
Summary
The security policies page said the worker publishes pod_creation_failed when the namespace quota refuses a pod. #428 removed that event, so the sentence pointed at something that no longer exists (policies.md).
Changes
The sentence now says what happens: the execution scheduler stores the execution as failed with error type system_error (execution_scheduler.py).
Type of Change
- Bug fix (non-breaking change that fixes an issue)
- New feature (non-breaking change that adds functionality)
- Breaking change (fix or feature that would cause existing functionality to change)
- Documentation update
- Refactoring (no functional changes)
- CI/CD or tooling changes
Test Plan
- Backend unit tests pass (
cd backend && uv run pytest tests/unit) - Frontend unit tests pass (
cd frontend && npm run test) - Backend E2E tests pass (
docker compose exec -T backend sh -c 'uv sync --group test --no-dev --frozen --no-install-project --no-build && pytest tests/e2e') - Frontend E2E tests pass (
cd frontend && npm run test:e2e) - API spec and client regenerated if routes or schemas changed (
./deploy.sh openapi, then./deploy.sh types), never edited by hand - Manual testing performed
Validation: docs only; CI's docs build checks it.
Checklist
- My code follows the project's style guidelines
- I have run
pre-commit run --all-filesand all checks pass - I have added tests that prove my fix/feature works
- I have updated documentation if needed
- My changes don't introduce new warnings
Summary by cubic
Fixes the security policies docs, which claimed the worker publishes pod_creation_failed when a pod is refused by the namespace quota. Since #428 removed that event, the docs now state what actually happens: the execution scheduler records the execution as failed with error type system_error.