Repository navigation
fix(OMN-14028): raise hot runtime service memory caps - #2221
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughMemory resource limits and reservations were increased for three services (agent-actions-consumer, skill-lifecycle-consumer, intelligence-api) in individual catalog service YAML files and mirrored in docker-compose.infra.yml. A new unit test validates these expanded memory limits and reservations in the compose file. ChangesService Memory Limit Increases
Estimated code review effort: 1 (Trivial) | ~5 minutes Sequence Diagram(s)Not applicable. Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested labels: infra, configuration Suggested reviewers: infrastructure team Poem: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Merge commits are not allowed on this repository
Summary
Verification
uv run pytest tests/unit/infra/test_compose_invariants.py -quv run ruff check tests/unit/infra/test_compose_invariants.pyuv run ruff format tests/unit/infra/test_compose_invariants.py --checkDeploy gate / post-merge validation
docker inspect --format '{{.HostConfig.Memory}}' omninode-agent-actions-consumer omninode-skill-lifecycle-consumer omnibase-intelligence-apidocker stats --no-streamand confirm the three services stay below 70% during normal load.Evidence-Ticket: OMN-14028
Evidence-Source: OCC#3649
Summary by CodeRabbit
New Features
Tests