Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(devcontainer): update image: v1.0.6 #2802

Merged
merged 1 commit into from
Dec 12, 2024
Merged

chore(devcontainer): update image: v1.0.6 #2802

merged 1 commit into from
Dec 12, 2024

Conversation

tarrencev
Copy link
Contributor

@tarrencev tarrencev commented Dec 12, 2024

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features
    • Updated Docker image version to enhance development and CI workflows.
    • Introduced a new testing job for improved functionality.
  • Bug Fixes
    • Ensured proper execution of the katana process in the CI workflow.
  • Chores
    • Updated various workflow configurations to use the latest Docker image version across multiple jobs.

Copy link

coderabbitai bot commented Dec 12, 2024

Walkthrough

Ohayo, sensei! This pull request introduces updates to the Docker image version in various configuration files related to a Rust development environment. The image version has been incremented from v1.0.5 to v1.0.6 in the .devcontainer/devcontainer.json, .github/workflows/bench.yml, .github/workflows/ci.yml, and .github/workflows/release-dispatch.yml files. Additionally, the CI workflow has been enhanced with a new testing job and modifications to existing jobs, while the overall structure remains unchanged.

Changes

File Change Summary
.devcontainer/devcontainer.json Updated Docker image version from v1.0.5 to v1.0.6.
.github/workflows/bench.yml Updated Docker image version from v1.0.5 to v1.0.6 for jobs bench-katana and bench-sozo.
.github/workflows/ci.yml Updated Docker image version from v1.0.5 to v1.0.6 across jobs: test, ensure-wasm, dojo-core-test, dojo-spawn-and-move-example-test, clippy, fmt, docs. Added test-hurl job. Modified ensure-docker job to check for katana process.
.github/workflows/release-dispatch.yml Updated Docker image version from v1.0.5 to v1.0.6 in the propose-release job.

Possibly related PRs

Suggested reviewers

  • glihm

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Experiment)
  • @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.

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: 0

🧹 Outside diff range and nitpick comments (2)
.github/workflows/ci.yml (2)

Line range hint 98-106: Consider enhancing the Katana process health check, sensei!

While adding a process health check is valuable, the current implementation using sleep could be more robust. Consider:

  1. Adding a timeout to prevent hanging
  2. Using a more reliable way to check process readiness (e.g., checking API endpoint)

Here's a suggested improvement:

- ./katana &
- KATANA_PID=$!
- sleep 2
- if ! kill -0 $KATANA_PID; then
-   echo "Katana exited with an error"
-   exit 1
- fi
- kill $KATANA_PID
+ ./katana & 
+ KATANA_PID=$!
+ TIMEOUT=30
+ while [ $TIMEOUT -gt 0 ]; do
+   if curl -s http://127.0.0.1:5050 >/dev/null; then
+     echo "Katana is ready"
+     kill $KATANA_PID
+     exit 0
+   fi
+   sleep 1
+   TIMEOUT=$((TIMEOUT-1))
+ done
+ echo "Katana failed to start within timeout"
+ kill $KATANA_PID
+ exit 1
🧰 Tools
🪛 actionlint (1.7.4)

32-32: label "ubuntu-latest-32-cores" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)


36-36: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


Ohayo! The Hurl version needs an update, sensei!

The workflow is using Hurl 3.0.0, but the latest stable version is 6.0.0. This significant version gap might include important bug fixes and improvements.

  • Update the Hurl installation command in .github/workflows/ci.yml:
- curl --location --remote-name https://github.com/Orange-OpenSource/hurl/releases/download/3.0.0/hurl_3.0.0_amd64.deb
+ curl --location --remote-name https://github.com/Orange-OpenSource/hurl/releases/download/6.0.0/hurl_6.0.0_amd64.deb
- sudo apt update && sudo apt install ./hurl_3.0.0_amd64.deb
+ sudo apt update && sudo apt install ./hurl_6.0.0_amd64.deb
🔗 Analysis chain

Line range hint 183-201: Ohayo! Let's verify the Hurl version and improve process management.

  1. The Hurl version is pinned to 3.0.0. Let's verify this is the latest stable version:

  2. The Katana process management could be improved:

- nohup /tmp/bins/katana --dev --dev.accounts 2 --dev.no-fee &
+ # Start Katana and wait for it to be ready
+ /tmp/bins/katana --dev --dev.accounts 2 --dev.no-fee > katana.log 2>&1 &
+ KATANA_PID=$!
+ echo "Waiting for Katana to be ready..."
+ TIMEOUT=30
+ while [ $TIMEOUT -gt 0 ]; do
+   if curl -s http://127.0.0.1:5050 >/dev/null; then
+     echo "Katana is ready"
+     break
+   fi
+   sleep 1
+   TIMEOUT=$((TIMEOUT-1))
+   if ! kill -0 $KATANA_PID 2>/dev/null; then
+     echo "Katana process died unexpectedly"
+     cat katana.log
+     exit 1
+   fi
+ done
+ if [ $TIMEOUT -eq 0 ]; then
+   echo "Katana failed to start within timeout"
+   cat katana.log
+   exit 1
+ fi
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check latest Hurl release version
gh api repos/Orange-OpenSource/hurl/releases/latest --jq .tag_name

Length of output: 74

🧰 Tools
🪛 actionlint (1.7.4)

32-32: label "ubuntu-latest-32-cores" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-22.04", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "macos-12-xl", "macos-12-xlarge", "macos-12-large", "macos-12", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file

(runner-label)


36-36: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ba8ff05 and 924abed.

📒 Files selected for processing (4)
  • .devcontainer/devcontainer.json (1 hunks)
  • .github/workflows/bench.yml (2 hunks)
  • .github/workflows/ci.yml (7 hunks)
  • .github/workflows/release-dispatch.yml (1 hunks)
✅ Files skipped from review due to trivial changes (3)
  • .github/workflows/release-dispatch.yml
  • .devcontainer/devcontainer.json
  • .github/workflows/bench.yml
🔇 Additional comments (1)
.github/workflows/ci.yml (1)

34-34: Ohayo sensei! Docker image version updates look consistent.

The Docker image version has been consistently updated to v1.0.6 across all jobs in the workflow.

Also applies to: 59-59, 126-126, 142-142, 157-157, 166-166, 175-175

Copy link

codecov bot commented Dec 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.75%. Comparing base (ba8ff05) to head (924abed).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2802   +/-   ##
=======================================
  Coverage   55.75%   55.75%           
=======================================
  Files         439      439           
  Lines       55572    55572           
=======================================
  Hits        30982    30982           
  Misses      24590    24590           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@glihm glihm merged commit 09dfaaf into main Dec 12, 2024
14 checks passed
@glihm glihm deleted the bump-devcontainer branch December 12, 2024 18:29
kariy pushed a commit that referenced this pull request Dec 13, 2024
Update devcontainer image: v1.0.6

Co-authored-by: glihm <[email protected]>
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