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

feat: introduce ibctesting feature #306

Merged
merged 1 commit into from
Nov 21, 2024
Merged

feat: introduce ibctesting feature #306

merged 1 commit into from
Nov 21, 2024

Conversation

beer-1
Copy link
Contributor

@beer-1 beer-1 commented Nov 21, 2024

Description

Bump movevm to v0.6.1 to introduce ibctesting feature.


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

@beer-1 beer-1 requested a review from a team as a code owner November 21, 2024 08:31
@beer-1 beer-1 self-assigned this Nov 21, 2024
Copy link

coderabbitai bot commented Nov 21, 2024

📝 Walkthrough

Walkthrough

The pull request updates the Dockerfile to change the version of the LIBMOVEVM library from v0.6.0 to v0.6.1. This modification is made in the ENV declaration, which specifies the library version for the build process. The overall structure and commands of the Dockerfile remain unchanged, ensuring that the build process for the Go project and the final image configuration are preserved.

Changes

File Change Summary
Dockerfile Updated LIBMOVEVM_VERSION from v0.6.0 to v0.6.1

Possibly related PRs

Poem

In the Dockerfile, a change so bright,
LIBMOVEVM's version takes flight.
From v0.6.0 to v0.6.1,
A simple tweak, but oh, such fun!
Building with care, the code will run,
Hopping along, our work is done! 🐇✨


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

Dependency Review

The following issues were found:
  • ✅ 0 vulnerable package(s)
  • ✅ 0 package(s) with incompatible licenses
  • ✅ 0 package(s) with invalid SPDX license definitions
  • ⚠️ 1 package(s) with unknown licenses.
See the Details below.

License Issues

go.mod

PackageVersionLicenseIssue Type
github.com/initia-labs/movevm0.6.1NullUnknown License
Denied Licenses: GPL-1.0-or-later, LGPL-2.0-or-later

OpenSSF Scorecard

PackageVersionScoreDetails
gomod/github.com/initia-labs/movevm 0.6.1 UnknownUnknown

Scanned Files

  • go.mod

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

🧹 Outside diff range and nitpick comments (2)
Dockerfile (2)

Line range hint 24-26: Implement hash verification for downloaded libraries

The commented-out hash verification should be implemented to ensure the integrity of downloaded libraries.

Consider uncommenting and implementing the hash verification:

 wget -O /lib/libmovevm_muslc.${ARCH}.a https://github.com/initia-labs/movevm/releases/download/${LIBMOVEVM_VERSION}/libmovevm_muslc.${ARCH}.a; \
 wget -O /lib/libcompiler_muslc.${ARCH}.a https://github.com/initia-labs/movevm/releases/download/${LIBMOVEVM_VERSION}/libcompiler_muslc.${ARCH}.a; \
 cp /lib/libmovevm_muslc.${ARCH}.a /lib/libmovevm_muslc.a; \
-cp /lib/libcompiler_muslc.${ARCH}.a /lib/libcompiler_muslc.a
+cp /lib/libcompiler_muslc.${ARCH}.a /lib/libcompiler_muslc.a; \
+echo "${EXPECTED_MOVEVM_HASH} /lib/libmovevm_muslc.${ARCH}.a" | sha256sum -c; \
+echo "${EXPECTED_COMPILER_HASH} /lib/libcompiler_muslc.${ARCH}.a" | sha256sum -c

You'll need to add the hash variables at the top of the Dockerfile:

+ARG EXPECTED_MOVEVM_HASH="<hash-value-here>"
+ARG EXPECTED_COMPILER_HASH="<hash-value-here>"

Line range hint 1-53: Consider using COPY --link for better build performance

While reviewing the multi-stage build setup, I noticed an opportunity for optimization.

Consider using COPY --link for the final binary copy to improve build performance:

-COPY --from=go-builder /code/build/initiad /usr/local/bin/initiad
+COPY --link --from=go-builder /code/build/initiad /usr/local/bin/initiad

This optimization uses mount points instead of copying data during build time, resulting in faster builds and reduced disk usage.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 0d67cfd and ee2c62b.

⛔ Files ignored due to path filters (2)
  • go.mod is excluded by !**/*.mod
  • go.sum is excluded by !**/*.sum, !**/*.sum
📒 Files selected for processing (1)
  • Dockerfile (1 hunks)

@@ -6,7 +6,7 @@ ARG TARGETARCH
ARG GOARCH

# See https://github.com/initia-labs/movevm/releases
ENV LIBMOVEVM_VERSION=v0.6.0
ENV LIBMOVEVM_VERSION=v0.6.1
Copy link

Choose a reason for hiding this comment

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

💡 Codebase verification

Required library artifacts are missing for movevm v0.6.1

The version v0.6.1 was released on 2024-11-21, but the required library artifacts are not available in the release:

  • ✗ libmovevm_muslc.x86_64.a not found
  • ✗ libcompiler_muslc.x86_64.a not found
  • ✗ libmovevm_muslc.aarch64.a not found
  • ✗ libcompiler_muslc.aarch64.a not found

This will cause the Docker build to fail. Please ensure the required library artifacts are published to the release before updating the version.

🔗 Analysis chain

Verify movevm v0.6.1 release and its compatibility

The version update from v0.6.0 to v0.6.1 needs verification to ensure stability and compatibility.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the movevm v0.6.1 release and required artifacts

# Check if the release exists and get release info
echo "Checking release v0.6.1..."
gh api repos/initia-labs/movevm/releases/tags/v0.6.1 | jq -r '.name, .prerelease, .published_at'

# Verify the existence of required library artifacts for both architectures
echo -e "\nChecking required artifacts..."
for ARCH in "x86_64" "aarch64"; do
  for LIB in "libmovevm_muslc" "libcompiler_muslc"; do
    URL="https://github.com/initia-labs/movevm/releases/download/v0.6.1/${LIB}.${ARCH}.a"
    if curl --output /dev/null --silent --head --fail "$URL"; then
      echo "${LIB}.${ARCH}.a exists"
    else
      echo "${LIB}.${ARCH}.a not found"
    fi
  done
done

Length of output: 1822

@beer-1 beer-1 merged commit 8a3d125 into main Nov 21, 2024
8 of 9 checks passed
@beer-1 beer-1 deleted the feat/ibctesting branch November 21, 2024 08:50
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.

1 participant