Repository navigation
docs: a pod over the namespace quota fails its execution - #440
Merged
Merged
Conversation
…n_failed no longer exists #428 removed the event, and the security policies page still named it.
HardMax71
enabled auto-merge (squash)
October 22, 2026 11:49
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
Bot
added
the
documentation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The security policies page said the worker publishes
pod_creation_failedwhen 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
failedwith error typesystem_error(execution_scheduler.py).Type of Change
Test Plan
cd backend && uv run pytest tests/unit)cd frontend && npm run test)docker compose exec -T backend sh -c 'uv sync --group test --no-dev --frozen --no-install-project --no-build && pytest tests/e2e')cd frontend && npm run test:e2e)./deploy.sh openapi, then./deploy.sh types), never edited by handValidation: docs only; CI's docs build checks it.
Checklist
pre-commit run --all-filesand all checks passSummary by cubic
Fixes the security policies docs, which claimed the worker publishes
pod_creation_failedwhen 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 asfailedwith error typesystem_error.Written for commit e37dea7. Summary will update on new commits.