chore: replace v6.0 binary with v6.1 #643
Conversation
WalkthroughThe recent updates to the Changes
Poem
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Additionally, you can add CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (2)
- cosmovisor.Dockerfile (2 hunks)
- cosmovisor_lite.Dockerfile (2 hunks)
Additional comments not posted (4)
cosmovisor.Dockerfile (2)
13-13: Verify the new base image integration.The new base image
ghcr.io/functionx/fx-core:6.1.0is correctly introduced asfxv6. Ensure that this image is available and correctly configured for your use case.
34-34: Ensure correct binary path forfxcored.The COPY command for
fxcoredfromfxv6to/root/.fxcore/cosmovisor/upgrades/v6.0.x/bin/is correctly formatted. Verify that this path aligns with your upgrade strategy and that the binary is correctly placed.Verification successful
Binary path for
fxcoredis correctly aligned with the upgrade strategy.The
COPYcommand incosmovisor.Dockerfilecorrectly placesfxcoredin/root/.fxcore/cosmovisor/upgrades/v6.0.x/bin/, and this path is consistently referenced in the repository. No issues found.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the correct placement of the `fxcored` binary. # Test: Check if the binary is correctly placed in the Docker image. docker run --rm ghcr.io/functionx/fx-core:6.1.0 ls /usr/bin/fxcoredLength of output: 143
Script:
#!/bin/bash # Find the Dockerfile to verify the `COPY` command for `fxcored` fd 'cosmovisor.Dockerfile' --exec cat {} # Search for any references to the upgrade path in the repository rg '/root/.fxcore/cosmovisor/upgrades/v6.0.x/bin/fxcored'Length of output: 1792
cosmovisor_lite.Dockerfile (2)
34-34: Ensure correct binary path forfxcored.The COPY command for
fxcoredfromfxv6to/root/.fxcore/cosmovisor/upgrades/v6.0.x/bin/is correctly formatted. Verify that this path aligns with your upgrade strategy and that the binary is correctly placed.Verification successful
Binary path for
fxcoredis correctly used.The path
/root/.fxcore/cosmovisor/upgrades/v6.0.x/bin/fxcoredis consistently used in the Dockerfiles, aligning with the upgrade strategy. This confirms that the binary is correctly placed according to the intended design. No further action is needed.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the correct placement of the `fxcored` binary. # Test: Check if the binary is correctly placed in the Docker image. docker run --rm ghcr.io/functionx/fx-core:6.1.0 ls /usr/bin/fxcoredLength of output: 143
Script:
#!/bin/bash # Search for occurrences of the binary path in the codebase to verify its usage. rg '/root/.fxcore/cosmovisor/upgrades/v6.0.x/bin/fxcored' --context 5Length of output: 2023
13-13: Verify the new base image integration.The new base image
ghcr.io/functionx/fx-core:6.1.0is correctly introduced asfxv6. Ensure that this image is available and correctly configured for your use case.
|
mg |
Summary by CodeRabbit
fxcoredbinary in bothcosmovisorandcosmovisor_lite.fxcoredbinary.