chore: upgrade handler for v6_6-rc1 for canon-4 network

[gsk967]

Description

1. Bid duration for auction is 4 hours on canon-4 network

---

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
• added ! to the type prefix if API or client breaking change
• added appropriate labels to the PR
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• 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
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

Summary by CodeRabbit

• New Features

  • Introduced a new release candidate upgrade (v6.6-rc1) for the testnet, enhancing the upgrade registration process.
  • Adjusted auction parameters, including setting a new bid duration of 4 hours to improve auction mechanics.

• Bug Fixes

  • Added comments to indicate future checks on auction fee parameters, ensuring robust financial mechanisms.

• Documentation

  • Included clarifying comments about changes to bidding durations and parameter adjustments in the auction system.

[coderabbitai]

Walkthrough

The recent changes enhance the upgrade process within the Umee application, transitioning to a more structured strategy for release candidates. Key updates include renaming upgrade functions to reflect their test nature, modifying auction parameters to optimize bidding durations, and introducing comments that suggest further validations post-upgrade. These adjustments indicate a proactive approach to system stability and financial management within the auction mechanisms.

Changes

File	Change Summary
app/upgrades.go	Replaced registerUpgrade6_6 with registerUpgrade6_6RC1 for testnet upgrades and adjusted upgrade plan name. Enhanced logic to manage auction fee parameters.
x/auction/genesis.go	Modified BidDuration in DefaultGenesis from 14 days to 4 hours, reflecting changes for the v6.6 upgrade. Comments added for clarity on auction processing.
x/auction/msgs.go	Added comment for future verification of MinRewardsBid post-upgrade; no changes to logic or functionality.

Poem

🐇 In the garden of upgrades, we leap and we bound,
New paths to explore, where treasures are found.
With a wink and a nod, we adjust and refine,
To make our auction blooms ever so fine.
Hopping through changes, we celebrate cheer,
For a vibrant new future is surely near! 🌼✨

---

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.
  • @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 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.

[codecov]

Codecov Report

Attention: Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 62.55%. Comparing base (7f05ad4) to head (6f46c5f).
Report is 516 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #2574       +/-   ##
===========================================
- Coverage   75.38%   62.55%   -12.84%     
===========================================
  Files         100      275      +175     
  Lines        8025    16035     +8010     
===========================================
+ Hits         6050    10031     +3981     
- Misses       1589     5231     +3642     
- Partials      386      773      +387     

Files	Coverage Δ
app/upgrades.go	48.50% <100.00%> (ø)
x/auction/msgs.go	50.00% <ø> (ø)
x/auction/genesis.go	0.00% <0.00%> (ø)

... and 238 files with indirect coverage changes

[coderabbitai]

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 17328ba and dca3b5e.

Files selected for processing (3)

• app/upgrades.go (1 hunks)
• x/auction/genesis.go (1 hunks)
• x/auction/msgs.go (1 hunks)

Files skipped from review due to trivial changes (1)

• x/auction/msgs.go

Additional context used

GitHub Check: codecov/patch

x/auction/genesis.go

[warning] 15-15: x/auction/genesis.go#L15
Added line #L15 was not covered by tests

Additional comments not posted (4)

x/auction/genesis.go (2)

Line range hint 17-29:
LGTM!

The Validate function correctly validates the BidDuration and other parameters.

Tools

GitHub Check: codecov/patch

[warning] 15-15: x/auction/genesis.go#L15
Added line #L15 was not covered by tests

---

13-15: Verify the correctness of the new BidDuration value.

The BidDuration has been changed from 14 days to 4 hours. Ensure this change aligns with the requirements for the canon-4 network.

Verification successful

---

The new BidDuration value of 4 hours is correct and consistent with the system requirements.

The change from 14 days to 4 hours for the BidDuration parameter is within the acceptable range (60 seconds to 180 days) and aligns with the specific requirements for the canon-4 network.

• The new value is validated correctly in the code.
• The change is specific to the canon-4 network as mentioned in the comment.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the correctness of the new `BidDuration` value.

# Test: Search for the usage of `BidDuration` to ensure the new value aligns with system requirements.
rg --type go -A 5 'BidDuration'

Length of output: 5261

Tools

GitHub Check: codecov/patch

[warning] 15-15: x/auction/genesis.go#L15
Added line #L15 was not covered by tests

app/upgrades.go (2)

61-78: LGTM!

The code changes are approved.

---

57-58: Verify the correctness of the new upgrade handler.

The new upgrade handler registerUpgrade6_6RC1 has been added for the canon-4 network. Ensure this change aligns with the requirements for the testnet.