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

fix: avoid build fail when make localnet-build-env #20671

Merged
merged 1 commit into from
Jun 14, 2024

Conversation

mmsqe
Copy link
Contributor

@mmsqe mmsqe commented Jun 14, 2024

Description

Closes: #XXXX


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 (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • 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.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

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

Summary by CodeRabbit

  • Chores
    • Updated Docker build context to reflect new module location for consistency and improved maintainability.

@mmsqe mmsqe requested a review from a team as a code owner June 14, 2024 10:13
Copy link
Contributor

coderabbitai bot commented Jun 14, 2024

Walkthrough

Walkthrough

The changes migrate the server/v2/core module to core/testing within the Docker build context to better align the project structure. This involves updating the paths in the Dockerfile where the module dependencies are copied.

Changes

File Change Summary
.../images/simd-env/Dockerfile Updated copy instructions to reflect module path changes.

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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
Contributor

@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 (3)
contrib/images/simd-env/Dockerfile (3)

Line range hint 3-3: Pin versions in apk add to ensure reproducibility.

- RUN apk add build-base git linux-headers
+ RUN apk add build-base=latest git=latest linux-headers=latest

Also, consider using the --no-cache option to avoid unnecessary cache storage:

- RUN apk add build-base git linux-headers
+ RUN apk add --no-cache build-base git linux-headers

Line range hint 38-38: Always tag the version of an image explicitly to ensure consistency.

- FROM alpine AS run
+ FROM alpine:latest AS run

Line range hint 39-39: Pin versions in apk add to ensure reproducibility.

- RUN apk add bash curl jq
+ RUN apk add bash=latest curl=latest jq=latest

Also, consider using the --no-cache option to avoid unnecessary cache storage:

- RUN apk add bash curl jq
+ RUN apk add --no-cache bash curl jq
Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between fa45e10 and 3192c0a.

Files selected for processing (1)
  • contrib/images/simd-env/Dockerfile (1 hunks)
Additional context used
Hadolint
contrib/images/simd-env/Dockerfile

[warning] 3-3: Pin versions in apk add. Instead of apk add <package> use apk add <package>=<version> (DL3018)


[info] 3-3: Use the --no-cache switch to avoid the need to use --update and remove /var/cache/apk/* when done installing packages (DL3019)


[warning] 38-38: Always tag the version of an image explicitly (DL3006)


[warning] 39-39: Pin versions in apk add. Instead of apk add <package> use apk add <package>=<version> (DL3018)


[info] 39-39: Use the --no-cache switch to avoid the need to use --update and remove /var/cache/apk/* when done installing packages (DL3019)

Additional comments not posted (1)
contrib/images/simd-env/Dockerfile (1)

30-30: Ensure the new module path in COPY command is correct and accessible.

Verification successful

The directory "core/testing" exists, and both "go.mod" and "go.sum" files are present within it. The COPY command in the Dockerfile should work correctly.

  • contrib/images/simd-env/Dockerfile, line 30
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the new module path is accessible.
# Test: Check if the module path exists.
if [ -d "core/testing" ]; then
  echo "Directory exists."
else
  echo "Directory does not exist."
fi

Length of output: 70



Script:

#!/bin/bash
# Description: Verify the existence of go.mod and go.sum in the core/testing directory.
# Test: Check if the files exist.
if [ -f "core/testing/go.mod" ] && [ -f "core/testing/go.sum" ]; then
  echo "Both files exist."
else
  if [ ! -f "core/testing/go.mod" ]; then
    echo "go.mod does not exist."
  fi
  if [ ! -f "core/testing/go.sum" ]; then
    echo "go.sum does not exist."
  fi
fi

Length of output: 110

Merged via the queue into cosmos:main with commit 05dd24d Jun 14, 2024
62 checks passed
alpe added a commit that referenced this pull request Jun 17, 2024
* main:
  feat(tx): port simappv2 changes (#20648)
  build(deps): Bump github.com/spf13/cobra from 1.8.0 to 1.8.1 (#20682)
  chore(proto): fix comments (#20679)
  (serverv2/cometbft) Commands support both json and yaml output (#20670)
  fix(x/staking,x/auth):  regenerate mock to fix test (#20684)
  docs: ADR 074: Msg v2 (#20618)
  fix: nested multisig signatures using CLI (#20438)
  chore: fix spelling errors (#20674)
  fix: align Dockerfile for build-push-action (#20672)
  fix: avoid build fail when make localnet-build-env (#20671)
  build(deps): Bump bufbuild/buf-setup-action from 1.32.2 to 1.33.0 (#20669)
  chore: make function comment match function names (#20666)
  chore(consensus): add cometInfo to consensus  (#20615)
  chore: fix typos (#20662)
  fix: Properly parse json in the wait-tx command. (#20631)
  fix(sims): check before sending RotateConsPubKey (#20659)
  test(types/address): add unit tests for the file types/address.go  (#20237)
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.

3 participants