Skip to content

devcontainer: bump node version to 22 and update feature installation#1017

Merged
undefined-moe merged 3 commits into
hydro-dev:masterfrom
criyle:master
Jul 18, 2025
Merged

devcontainer: bump node version to 22 and update feature installation#1017
undefined-moe merged 3 commits into
hydro-dev:masterfrom
criyle:master

Conversation

@criyle

@criyle criyle commented Jul 17, 2025

Copy link
Copy Markdown
Contributor
  • bump dev container version to 22
  • use dev container feature gh-release to install sandbox and apt packages

Summary by CodeRabbit

  • Chores
    • Updated development container to use newer base images and simplified setup steps.
    • Replaced installation of certain binaries and packages with standardized devcontainer features.
    • Updated MongoDB service to use the latest image.
    • Removed two VS Code extensions from the recommended list.
    • Adjusted service startup commands and added volume mounts for improved development environment consistency.

@coderabbitai

coderabbitai Bot commented Jul 17, 2025

Copy link
Copy Markdown

Walkthrough

The development container setup was modified by updating the base image from typescript-node:20-bookworm to 22-bookworm and removing the installation and entrypoint configuration for the sandbox binary. Global installation of yarn and system packages gcc and g++ was removed from the Dockerfile. Directory creation commands were simplified, and configuration files for Hydro were added. The devcontainer configuration removed two VS Code extension recommendations and added features to install the go-judge binary and the gcc and g++ packages. The Docker Compose configuration removed the version declaration, updated the MongoDB image from version 4 to 8, added a node_modules volume, and changed the hydro service command to run go-judge.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fec9eeb and 2523b78.

📒 Files selected for processing (1)
  • .devcontainer/Dockerfile (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • .devcontainer/Dockerfile
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: build
  • GitHub Check: Analyze (javascript)

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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (3)
.devcontainer/Dockerfile (1)

3-6: Minor: favour heredoc for multi-line JSON ‑ improves readability & escapes.

-RUN mkdir -p /root/.hydro /data/file && \
-    chown -R root:root /root /root/.hydro /data/file && \
-    echo '{"uri":"mongodb://mongo/hydro"}' > /root/.hydro/config.json && \
-    echo '["@hydrooj/ui-default","@hydrooj/hydrojudge"]' > /root/.hydro/addon.json
+RUN install -d -o root -g root /root/.hydro /data/file \
+ && cat <<'EOF' > /root/.hydro/config.json
+{"uri":"mongodb://mongo/hydro"}
+EOF
+ && cat <<'EOF' > /root/.hydro/addon.json
+["@hydrooj/ui-default","@hydrooj/hydrojudge"]
+EOF
.devcontainer/devcontainer.json (2)

21-34: Avoid double-installing Node – the base image already ships with Node 22.

Adding the Node dev-container feature forces an extra install layer and lengthens build time.
Unless you need a different version or extra options, drop the feature block to keep the image slim.

-		"ghcr.io/devcontainers/features/node:1": {}

35-35: postCreateCommand assumes global yarn; ensure it’s present with Node 22.

Recent Node images rely on Corepack and don’t install classic Yarn v1 globally. Either prepend corepack enable or install Yarn explicitly.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4165e9b and 4f1be1a.

📒 Files selected for processing (3)
  • .devcontainer/Dockerfile (1 hunks)
  • .devcontainer/devcontainer.json (1 hunks)
  • .devcontainer/docker-compose.yml (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build
🔇 Additional comments (3)
.devcontainer/docker-compose.yml (1)

17-18: Verify that replacing Hydro’s default start-up with go-judge is intentional.

command: go-judge will execute the Go binary and not start the Node-based Hydro server (yarn start / node index.js).
If the intention was to add the judge service, consider declaring it as a separate service instead of hijacking hydro.

.devcontainer/Dockerfile (1)

1-1: Confirm Hydro supports Node 22.

The base image jump from v20 → v22 can surface native-addon ABI breaks and engine-range mismatches ("engines": {"node": ">=14 <=20"} etc.).
Run the test suite or yarn install --check-engines to ensure compatibility.

.devcontainer/devcontainer.json (1)

22-26: Validate binaryNames schema for gh-release feature.

The feature spec expects an array (["go-judge"]), not a string. An incorrect type silently skips symlinking, leaving the binary inaccessible in $PATH.

Comment thread .devcontainer/docker-compose.yml Outdated

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 49cdb4a and fec9eeb.

📒 Files selected for processing (3)
  • .devcontainer/Dockerfile (1 hunks)
  • .devcontainer/devcontainer.json (1 hunks)
  • .devcontainer/docker-compose.yml (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • .devcontainer/docker-compose.yml
  • .devcontainer/devcontainer.json
🧰 Additional context used
🪛 Hadolint (2.12.0)
.devcontainer/Dockerfile

[error] 5-5: unexpected '{'
expecting '#', '', ADD, ARG, CMD, COPY, ENTRYPOINT, ENV, EXPOSE, FROM, HEALTHCHECK, LABEL, MAINTAINER, ONBUILD, RUN, SHELL, STOPSIGNAL, USER, VOLUME, WORKDIR, a pragma, at least one space, or end of input

(DL1000)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: CodeQL
  • GitHub Check: build
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (1)
.devcontainer/Dockerfile (1)

1-1: Confirm Node 22 compatibility

Bumping the base image to typescript-node:22-bookworm is forward-looking, but Hydro’s runtime and any pinned native dependencies must compile against the Node 22 ABI. Please ensure CI covers this path and no node-gyp recompilation failures pop up.

Comment thread .devcontainer/Dockerfile Outdated
@undefined-moe undefined-moe merged commit a3226f7 into hydro-dev:master Jul 18, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants