Problem: cosmovisor in test is out dated

[yihuang]

new version cosmovisor support graceful shutdown

Solution:

• update cosmovisor
• adapt the test case

👮🏻👮🏻👮🏻 !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! 👮🏻👮🏻👮🏻

PR Checklist:

• Have you read the CONTRIBUTING.md?
• Does your PR follow the C4 patch requirements?
• Have you rebased your work on top of the latest master?
• Have you checked your code compiles? (make)
• Have you included tests for any non-trivial functionality?
• Have you checked your code passes the unit tests? (make test)
• Have you checked your code formatting is correct? (go fmt)
• Have you checked your basic code style is fine? (golangci-lint run)
• If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
• If your changes affect the client infrastructure, have you run the integration test?
• If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
• If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
• If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

Thank you for your code, it's appreciated! :)

Summary by CodeRabbit

• New Features
  • Upgraded Cosmovisor to version 1.5.0 in integration tests.
  • Introduced a new method for creating tarballs without following symbolic links to avoid duplicates and ensure standard extraction results.
• Bug Fixes
  • Updated upgrade-test-package configuration to correctly include specific versions and directories.
• Refactor
  • Simplified the tarball creation logic by removing adjustments related to symbolic links and ownership/permissions.
  • Modified the cosmovisor start command to cosmovisor run start in integration tests for enhanced functionality.
• Chores
  • Removed the cosmos-sdk entry from sources, streamlining the build process.

[coderabbitai]

Walkthrough

This update orchestrates the integration of cosmovisor version 1.5.0, streamlining testing procedures and simplifying tarball generation. It enhances the packaging of cosmovisor via Nix, ensuring deployment efficiency and standardization.

Changes

Files	Change Summaries
CHANGELOG.md	Added cosmovisor 1.5.0 upgrade for integration tests.
flake.nix	Simplified bundle creation by removing symbolic link logic.
.../upgrade-test-package.nix, nix/build_overlay.nix	Updated paths and added overlay for tarball creation without symbolic links.
integration_tests/test_upgrade.py	Adjusted cosmovisor commands and improved tarball extraction setup.
nix/cosmovisor.nix, nix/default.nix	Introduced cosmovisor 1.5.0 build and packaging with Nix.
nix/sources.json	Removed cosmos-sdk entry.

🐇✨
In the realm of code and Nix,
Where tarball tricks now fix.
Cosmovisor shines anew,
Streamlined, ready, through and through.
Changes swift, improvements keen,
A brighter code world now seen.
🌟🚀

---

Recent Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 1aea999 and fb1a4ee.

Files selected for processing (8)

• CHANGELOG.md (1 hunks)
• flake.nix (1 hunks)
• integration_tests/configs/upgrade-test-package.nix (1 hunks)
• integration_tests/test_upgrade.py (2 hunks)
• nix/build_overlay.nix (1 hunks)
• nix/cosmovisor.nix (1 hunks)
• nix/default.nix (1 hunks)
• nix/sources.json (1 hunks)

Files skipped from review as they are similar to previous changes (7)

• flake.nix
• integration_tests/configs/upgrade-test-package.nix
• integration_tests/test_upgrade.py
• nix/build_overlay.nix
• nix/cosmovisor.nix
• nix/default.nix
• nix/sources.json

Additional comments not posted (1)

CHANGELOG.md (1)

7-7: The entry about upgrading cosmovisor to version 1.5.0 in integration tests is clear and accurately reflects the PR's objectives.

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

• X
• Mastodon
• Reddit
• LinkedIn

---

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

[coderabbitai]

Actionable comments posted: 1

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 16.47%. Comparing base (1aea999) to head (fb1a4ee).

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #1380       +/-   ##
===========================================
- Coverage   36.55%   16.47%   -20.09%     
===========================================
  Files         129       80       -49     
  Lines        9597     5124     -4473     
===========================================
- Hits         3508      844     -2664     
+ Misses       5712     4204     -1508     
+ Partials      377       76      -301     

see 73 files with indirect coverage changes

[mmsqe]

wow, didn't realize cosmovisor is this old

[yihuang]

wow, didn't realize cosmovisor is this old

it was in SDK 0.45