Skip to content

Conversation

@VSGic
Copy link
Contributor

@VSGic VSGic commented Jul 25, 2025

Summary by CodeRabbit

  • Chores
    • Updated the source for downloading the cronos binary to use the testnet version.

@coderabbitai
Copy link

coderabbitai bot commented Jul 25, 2025

Walkthrough

The Dockerfile was updated to change the download source for the cronos binary from the "v1.4.9" release to the "v1.4.9-testnet" release. The filename and URL were adjusted accordingly, while all other extraction and installation steps remain unchanged.

Changes

File(s) Change Summary
Dockerfile Updated cronos binary download URL and filename to "v1.4.9-testnet"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

The Dockerfile hops to a new testnet,
With URLs changed, the goal is set.
Cronos unpacks with a gentle cheer,
A fresh new version is finally here!
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/1.4.9-testnet-2

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 generate unit tests to generate unit tests for 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e8e65e5 and 0973916.

📒 Files selected for processing (1)
  • Dockerfile (1 hunks)
🧰 Additional context used
🪛 Checkov (3.2.334)
Dockerfile

[HIGH] 7-8: Ensure that certificate validation isn't disabled with wget

(CKV2_DOCKER_3)

⏰ 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: guardrails/scan

RUN mkdir -p /home/cronos/data && mkdir -p /home/cronos/config
RUN apt-get update -y && apt-get install wget curl procps net-tools jq lz4 -y
RUN cd /tmp && wget --no-check-certificate https://github.com/crypto-org-chain/cronos/releases/download/v1.4.9/cronos_1.4.9_Linux_x86_64.tar.gz && tar -xvf cronos_1.4.9_Linux_x86_64.tar.gz \
RUN cd /tmp && wget --no-check-certificate https://github.com/crypto-org-chain/cronos/releases/download/v1.4.9/cronos_1.4.9-testnet_Linux_x86_64.tar.gz && tar -xvf cronos_1.4.9_Linux_x86_64.tar.gz \
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Avoid --no-check-certificate unless absolutely necessary

Disabling TLS verification silences MITM-protection and triggers CVE scanners (CKV2_DOCKER_3).
If GitHub’s certificate problems are not expected, remove the flag; otherwise fetch the artifact with curl --proto '=https' --tlsv1.2 --location and pin the SHA256 to guarantee integrity.

🧰 Tools
🪛 Checkov (3.2.334)

[HIGH] 7-8: Ensure that certificate validation isn't disabled with wget

(CKV2_DOCKER_3)

🤖 Prompt for AI Agents
In Dockerfile at line 7, remove the wget option --no-check-certificate to avoid
disabling TLS verification. Instead, replace wget with curl using the flags
--proto '=https' --tlsv1.2 --location to securely fetch the file. Additionally,
add a step to verify the downloaded file's SHA256 checksum to ensure its
integrity before extraction.

Comment on lines +7 to 9
RUN cd /tmp && wget --no-check-certificate https://github.com/crypto-org-chain/cronos/releases/download/v1.4.9/cronos_1.4.9-testnet_Linux_x86_64.tar.gz && tar -xvf cronos_1.4.9_Linux_x86_64.tar.gz \
&& rm cronos_1.4.9_Linux_x86_64.tar.gz && mv ./* /home/cronos/
RUN chown -R cronos:cronos /home/cronos && chmod 1777 /tmp
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Archive name mismatch will break the build

The file you now download is cronos_1.4.9-testnet_Linux_x86_64.tar.gz, yet the subsequent tar -xvf and rm commands still reference cronos_1.4.9_Linux_x86_64.tar.gz.
At build time the tar step will fail with “cannot open: No such file or directory”, aborting the image build.

-RUN cd /tmp && wget --no-check-certificate https://github.com/crypto-org-chain/cronos/releases/download/v1.4.9/cronos_1.4.9-testnet_Linux_x86_64.tar.gz && tar -xvf cronos_1.4.9_Linux_x86_64.tar.gz \
-    && rm cronos_1.4.9_Linux_x86_64.tar.gz && mv ./* /home/cronos/
+RUN cd /tmp \
+ && wget --no-check-certificate https://github.com/crypto-org-chain/cronos/releases/download/v1.4.9-testnet/cronos_1.4.9-testnet_Linux_x86_64.tar.gz \
+ && tar -xvf cronos_1.4.9-testnet_Linux_x86_64.tar.gz \
+ && rm cronos_1.4.9-testnet_Linux_x86_64.tar.gz \
+ && mv ./* /home/cronos/

(Notice I also fixed the release path to /v1.4.9-testnet/; the current one still points to /v1.4.9/.)

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
RUN cd /tmp && wget --no-check-certificate https://github.com/crypto-org-chain/cronos/releases/download/v1.4.9/cronos_1.4.9-testnet_Linux_x86_64.tar.gz && tar -xvf cronos_1.4.9_Linux_x86_64.tar.gz \
&& rm cronos_1.4.9_Linux_x86_64.tar.gz && mv ./* /home/cronos/
RUN chown -R cronos:cronos /home/cronos && chmod 1777 /tmp
RUN cd /tmp \
&& wget --no-check-certificate https://github.com/crypto-org-chain/cronos/releases/download/v1.4.9-testnet/cronos_1.4.9-testnet_Linux_x86_64.tar.gz \
&& tar -xvf cronos_1.4.9-testnet_Linux_x86_64.tar.gz \
&& rm cronos_1.4.9-testnet_Linux_x86_64.tar.gz \
&& mv ./* /home/cronos/
RUN chown -R cronos:cronos /home/cronos && chmod 1777 /tmp
🧰 Tools
🪛 Checkov (3.2.334)

[HIGH] 7-8: Ensure that certificate validation isn't disabled with wget

(CKV2_DOCKER_3)

🤖 Prompt for AI Agents
In Dockerfile lines 7 to 9, the downloaded archive filename
cronos_1.4.9-testnet_Linux_x86_64.tar.gz does not match the filename used in the
tar and rm commands, causing build failure. Update the tar and rm commands to
reference cronos_1.4.9-testnet_Linux_x86_64.tar.gz instead of
cronos_1.4.9_Linux_x86_64.tar.gz. Also, ensure the download URL path matches the
testnet version /v1.4.9-testnet/ as corrected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants