Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe project updates Node.js versions in configuration, CI, Docker images, and Lambda runtime settings. Build images now run as the ChangesRuntime and local development updates
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install failed: dependency version conflict. Check your lock file or package.json. 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #129 +/- ##
==========================================
+ Coverage 99.71% 99.73% +0.01%
==========================================
Files 234 234
Lines 6346 6391 +45
Branches 1866 1900 +34
==========================================
+ Hits 6328 6374 +46
Misses 16 16
+ Partials 2 1 -1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
…when restarting server in development
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Dockerfile`:
- Line 1: Configure the Docker image to run as the non-root node user by adding
USER node after all installation steps. Ensure /build and any
application-written paths are owned by node before switching users.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: c7db598f-9c7d-4932-bcdb-dba37e555c84
📒 Files selected for processing (6)
Dockerfilebin/Dockerfilebin/deploy-bamboo.shbin/env/local_env.shbin/start-local.shcdk/rdfdb/docker/Dockerfile
|
The local, CI, and Docker runtimes are now Node 24, but deployed Lambdas still use NODEJS_22_X. We should also update this to lambda.Runtime.NODEJS_24_X so AWS also runs Krypton? |
| export RDF4J_PASSWORD="${RDF4J_PASSWORD:-rdf4j}" | ||
| export CMR_BASE_URL="${CMR_BASE_URL:-}" | ||
| export CMR_BASE_URL="${CMR_BASE_URL:-https://cmr.sit.earthdata.nasa.gov}" | ||
| export RDF4J_CONTAINER_MEMORY_LIMIT="${RDF4J_CONTAINER_MEMORY_LIMIT:-2048}" |
There was a problem hiding this comment.
This makes local CMR requests default to shared SIT, including write operations. Can we put this back to the empty deault?
There was a problem hiding this comment.
Reverted the default to empty
Done, now using v 24 |
Overview
What is the feature?
Update to use node version 24 (also node version in github workflow)
What is the Solution?
Update to use node 24
Ran 'npm audit fix'
Fix 'curl' not found when starting rdf4j server
Fix updating when change code in dev mode.
What areas of the application does this impact?
Node version and local development
Testing
Sanity test. Change code and restart server to verify updating.
Attachments
N/A
Checklist
Summary by CodeRabbit
Enhancements
Bug Fixes
curlto the RDF database container for required tooling support.