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

chore: release v7.1.0-rc1 #500

Merged
merged 1 commit into from
May 19, 2024
Merged

chore: release v7.1.0-rc1 #500

merged 1 commit into from
May 19, 2024

Conversation

zakir-code
Copy link
Contributor

@zakir-code zakir-code commented May 19, 2024

Summary by CodeRabbit

  • New Features

    • Introduced auto refund for bridge calls.
    • Added support for pre-compiled contracts in bridge calls.
    • Enabled IBC bridge calls to fxCore-EVM.
    • Implemented crosschain liquidity provider rewards.
  • Improvements

    • Enhanced bridge call functionality on EVM heterogeneous chains.
    • Updated max-tx-gas-wanted setting on upgrade.
  • Bug Fixes

    • Fixed validation issues for BypassMinFee.
  • Refactor

    • Updated log messages for upgrade migrations.
    • Refactored module address assignment in ERC20 keeper.
  • Chores

    • Updated version name to v7.1.x.

Copy link

coderabbitai bot commented May 19, 2024

Walkthrough

In version v7.1.0-rc1, major enhancements include support for bridge call auto refunds, pre-compiled contracts for bridge calls, and IBC bridge calls to fxCore-EVM. Improvements also enhance bridge call functionality on EVM heterogeneous chains. Bug fixes address validation of BypassMinFee and updating max-tx-gas-wanted during upgrades. Additionally, logging in upgrade handlers and module address assignments in the ERC20 keeper have been refined.

Changes

File Path Change Summary
CHANGELOG.md Documented new features, improvements, and bug fixes for version v7.1.0-rc1.
app/upgrades/v7/constants.go Updated UpgradeName from "v7.0.x" to "v7.1.x".
app/upgrades/v7/upgrade.go Enhanced log messages in CreateUpgradeHandler to include additional context information.
x/erc20/keeper/keeper.go Refactored moduleAddress assignment in the NewKeeper function for clarity.
src/bridge_utils.py, src/contract_utils.py, ... Added support for bridge call auto refunds, pre-compiled contracts, IBC bridge calls, and more.
src/validation_utils.py, src/upgrade_utils.py Added validation for BypassMinFee and updated max-tx-gas-wanted to 0 on upgrade.
src/cli.py Added layer2 module to crosschain CLI.

In the world of code, where bytes do flow,
Bridges now refund, and contracts grow.
Logs speak clearer, migrations in sight,
Upgrades shine bright, in the digital night.
With each new line, our features expand,
A rabbit's touch, in this coding land.
🌟🐇✨


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.

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.

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

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between dc6c756 and aedc828.
Files selected for processing (4)
  • CHANGELOG.md (1 hunks)
  • app/upgrades/v7/constants.go (1 hunks)
  • app/upgrades/v7/upgrade.go (1 hunks)
  • x/erc20/keeper/keeper.go (2 hunks)
Files skipped from review due to trivial changes (1)
  • app/upgrades/v7/constants.go
Additional Context Used
LanguageTool (8)
CHANGELOG.md (8)

Near line 108: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ... * Fix: WFX Token contract code * Fix: can not transfer shares when redelegate * Fix: ...


Near line 172: Possible typo: you repeated a word
Context: ...-gateway path * Fix Rest API query tx * Fix make install * Fix v2.1 upgrade migrate event * Fix parse ...


Near line 196: Loose punctuation mark.
Context: ... ### Features * RegisterERC20Proposal, RegisterCoinProposal, `ToggleTokenCon...


Near line 203: This phrase is redundant. Consider writing “cancel”.
Context: ... ### Bug Fixes * Fix gravity module cancel out batch panic ### Features * (fx/base) ...


Near line 255: Possible typo: you repeated a word
Context: ...les: feegrant、authz、feemarket、evm、erc20、migrate * Migrate modules: auth、bank、distribution、gov、sla...


Near line 267: Consider using either the past participle “renamed” or the present participle “renaming” here.
Context: ...mint update-validatorcommand has been rename to thefxcored tendermint unsafe-reset...


Near line 268: Consider using either the past participle “renamed” or the present participle “renaming” here.
Context: ...rmint update-node-keycommand has been rename to thefxcored tendermint unsafe-reset...


Near line 272: After the number ‘60’, use a plural noun. Did you mean “outputs”?
Context: ...ault is 60 * fxcored keys add command output add the EIP55 address * Remove Cli flag...

Additional comments not posted (4)
app/upgrades/v7/upgrade.go (2)

23-23: Enhanced logging by including the plan name provides better context during upgrades.


31-31: Consistent logging enhancement by including the module name at the completion of the upgrade.

x/erc20/keeper/keeper.go (1)

Line range hint 44-56: Refactoring to simplify moduleAddress initialization enhances readability. Ensure moduleAddress is not used before the nil check.

Verification successful

The verification confirms that moduleAddress is not used before the nil check.

  • moduleAddress is assigned a value and immediately checked for nil before any usage.
Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that `moduleAddress` is not used before the nil check.

# Test: Search for usage of `moduleAddress` before it's checked for nil.
rg --type go $'moduleAddress' x/erc20/keeper/keeper.go

Length of output: 249



Script:

#!/bin/bash
# Extract relevant lines from the file to verify the sequence of `moduleAddress` usage.
sed -n '41,48p' x/erc20/keeper/keeper.go

Length of output: 278

CHANGELOG.md (1)

38-57: Changelog entries for version v7.1.0-rc1 are well-organized and follow the established guidelines.

@zakir-code
Copy link
Contributor Author

mg

@zakir-code zakir-code merged commit 0bf0f2f into main May 19, 2024
9 checks passed
@zakir-code zakir-code deleted the zakir/release branch May 19, 2024 08:21
zakir-code pushed a commit to zakir-code/fx-core that referenced this pull request May 24, 2024
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.

None yet

1 participant