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

Bump cosmos-sdk to v0.46.13-pio-3 (from v0.46.13-pio-2). #1848

Merged
merged 3 commits into from
Feb 21, 2024

Conversation

SpicyLemon
Copy link
Contributor

@SpicyLemon SpicyLemon commented Feb 21, 2024

Description

This PR bumps cosmos-sdk to v0.46.13-pio-3 (from v0.46.13-pio-2).

This brings in the periodic vesting blocked address fix.


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md)
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Wrote unit and integration tests
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/)
  • Added relevant godoc comments.
  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Re-reviewed Files changed in the Github PR explorer
  • Review Codecov Report in the comment section below once CI passes

Summary by CodeRabbit

  • Chores
    • Updated cosmos-sdk version for improved performance and stability.

@SpicyLemon SpicyLemon requested a review from a team as a code owner February 21, 2024 20:46
Copy link
Contributor

coderabbitai bot commented Feb 21, 2024

Walkthrough

This update signifies a minor but important advancement in the cosmos-sdk version, transitioning from v0.46.13-pio-2 to v0.46.13-pio-3. The change indicates targeted enhancements or fixes within the SDK that could impact the performance, security, or functionality of related applications.

Changes

Files Affected Change Summary
go.mod, go.sum Updated cosmos-sdk version from pio-2 to pio-3

🐇✨
A tiny hop in code, a giant leap for 'block-kind',
From .2 to .3, what wonders we'll find.
Through cosmos we bound, with upgrades in tow,
On blockchain's vast meadow, our codebase does grow.
🚀🌌

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-tests for this file.
  • 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 tests 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 from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @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.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

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.

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 16fb638 and 7c8cfc6.
Files ignored due to path filters (2)
  • go.mod is excluded by: !**/*.mod
  • go.sum is excluded by: !**/*.sum
Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
Additional comments: 1
CHANGELOG.md (1)
  • 73-73: The changelog entry clearly documents the bump in cosmos-sdk version from v0.46.13-pio-2 to v0.46.13-pio-3, following the conventional format and providing clear context for the change.

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.

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 7c8cfc6 and 5bc191b.
Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • CHANGELOG.md

@SpicyLemon SpicyLemon enabled auto-merge (squash) February 21, 2024 20:49
@SpicyLemon SpicyLemon merged commit e8d71f6 into main Feb 21, 2024
36 checks passed
@SpicyLemon SpicyLemon deleted the dwedul/bump-sdk-to-v0.46.13-pio-3 branch February 21, 2024 20:55
SpicyLemon added a commit that referenced this pull request Feb 21, 2024
* Bump cosmos-sdk to v0.46.13-pio-3 (from v0.46.13-pio-2).

* Add changelog entry.
# Conflicts:
#	CHANGELOG.md
SpicyLemon added a commit that referenced this pull request Feb 22, 2024
…per-usd-mil), 1835 (transfer agents), 1843 (bid prices), 1846 (restricted coins/fee collector), 1848 (sdk to v0.46.13-pio-3). (#1849)

* Require new force_transfer access to do forced transfers. (#1831)

* [1829]: Add ACCESS_FORCE_TRANSFER entry to the Access enum.

* [1829]: Add some clarifications to the access entries.

* [1829]: Check the new force-transfer permission when doing a forced transfer.

* [1829]: Add changelog entry.

* [1892]: Clarify the deposit and withdraw permissions a bit.

* Add exchange commitments to CLI. (#1830)

* [1789]: Update cli for existing stuff that got some new fields.

* [1789]: Create the commit-funds command and the helper stuff for AccountAmount and NetAssetPrice entries.

* [1789]: Write the market-commitment-settle command.

* [1789]: Create the market-release-commitments command.

* [1789]: Create the market-accepting-commitments command.

* [1789]: Create the gov-close-market command.

* [1789]: Fix the placement of the accepting-orders stuff.

* [1789]: Create the market-intermediary-denom command.

* [1789]: Add a test helper to check if some events are in another list of events.

* [1789]: Unit tests on the commit funds command.

* [1789]: Add TODOs for the query commands.

* [1789]: Write all the query commands.

* [1789]: Unit tests on the rest of the cmd setups/makers.

* [1789]: Allow providing the commitment settlement as a file.

* [1789]: Unit tests on the query commands. Alter the commitment settlement fee calc setup to not require an admin arg when --file is provided.

* [1789]: Unit tests on the tx commands.

* [1789]: Add changelog entry.

* [1789]: Fix --inputs and --outputs flag description.

* [1789]: Add some flags missing from the market settle setup test case.

* [1789]: A couple small tweaks to the cli tests.

* Update msg-fees param nhash per mil to 40,000,000 ($0.025/hash). (#1833)

* In the tourmaline upgrade, update the msg-fees nhash/usd-mil to 40,000,000 = -bash.025/hash (currently 25,000,000 = -bash.04/hash).

* Update the comments on the MsgFees Params message to include the conversion formulas too.

* Update TestTourmaline to check for module migrations and inactive delegations log entries.

* Fix capitalization and punctuation of log messages in removeInactiveValidatorDelegations.

* Add punctuation to the log messages from convertNavUnits and add a done message.

* Add changelog entry.

* Allow bid order prices to not be evenly divisible by buyer settlement fee ratios. (#1843)

* Allow the bid price to not be evenly applicable to a fee ratio.

* Fix unit tests that broke because we loosened the bid order fee/price stuff.

* Add changelog entry.

* Update spec docs.

* Allow transfer agents to do exchange settlements with restricted coins. (#1835)

* [1834]: Add tourmaline-rc2 upgrade handler since I'm about to make a state-breaking change that'll require an upgrade.

* [1834]: Add context functions for passing in the transfer agent.

* [1834]: Pay attention to the newly available transfer agent in the send restriction. Move the deposit check to SendRestrictionFn (from validateSendDenom) since don't need to repeat that check for every denom. Add a check for withdraw on the from addr since that might now be a marker account. Tweak a couple error messages to distinguish them from eachother. In the transfer endpoint, if the destination is also a marker, check for deposit access on that marker.

* [1834]: Switch the TestAccountKeeperMintBurnCoins fix to provide the transfer agent instead of just bypassing the send restrictions.

* [1834]: If no force transfer, and coming from a marker, make sure the admin has withdraw on that marker. Unit tests on the TransferCoin function.

* [1834]: Unit tests on the send restriction function.

* [1834]: Set the transfer agent in the exchange stuff that does bank stuff.

* [1834]: Fix the unit tests that broke and add a couple new ones.

* [1834]: tiny tweak to a couple unit tests.

* [1834]: In AddSetNetAssetValues, emit the nav event even when the price denom's marker isn't found.

* [1834]: Tweak TestKeeper_WithdrawMarketFunds again to make it a little easier on test setup.

* [1834]: lint (kind of since it's in a test file that isn't linted, but whatever).

* [1834]: Add access validator functions to the marker to standardize the errors when an address doesn't have a certain role.

* [1834]: Remove redundant 'access' from error about not having access (the enum name starts with ACCESS_).

* [1834]: Standardize the no-access errors. In WithdrawCoins, if going to a marker, make sure they've got deposit on that marker. Require a marker to be active in ordr to send its funds.

* [1834]: Update TransferCoin. Add comment above authzHandler with the reason we don't check for withdraw and remove the check for withdraw.

* [1834]: Fix the error in validateSendDenom for sends to a marker to reference the correct denom and address.

* [1834]: Fix the tests that broke because I changed the error messages.

* [1834]: Update AddSetNetAssetValues. Try all entries even if an earlier one has an error. If the price marker does not exist, only emit the event if the nav is valid. Put some unit tests on that thing.

* [1834]: Add unit test on send restriction when we can't get attributes.

* [1834]: Fix some comments in the mocks, add a unit test making sure force-transfer access is ignored in the send restriction, and add force transfer to a couple access unit tests.

* [1834]: Update marker spec docs with all the recent chagnes.

* [1834]: For the exchange stuff, pay attention to blocked addresses in the off-chance one gets used.

* [1834]: Check that a marker is active before allowing a transfer.

* [1834]: In WithdrawCoins, make sure the recipient is not a bank blocked address.

* [1834]: Some tweaks to the spec docs to fix some typos, grammer, and flowchart stuff.

* [1834]: Redo the flows so that denied is on the left for all of them. Add some links between flows.

* [1834]: Fix the names of a bunch of keeper unit tests that claim to be testing account stuff.

* [1834]: Unit tests on WithdrawCoins and on Transfer of non-active coins.

* [1834]: Fix unit tests on WithdrawMarketFunds that broke because a call to BlockedAddr is now being made that wasn't expected previously. Add test for when the address is blocked.

* [1834]: Fix TestKeeper_SettleCommitments that broke because of the added calls to BlockedAddr that weren't previously expected.

* [1834]: Fix TestKeeper_DoTransfer that broke because we added calls to BlockedAddr that weren't listed as expected. Add a test for when an address is blocked.

* [1834]: Fix TestKeeper_SettleOrders that broke when I added calls to BlockedAddr.

* [1834]: Fix the FillAsks and FillBids unit tests that broke when I started calling BlockedAddr.

* [1834]: Remove TODO that's TODONE (unit tests on blocked addresses).

* [1834]: Update the exchange spec docs to include stuff about the transfer agent as well as a commitment settlement fee calc example.

* [1834]: Add changelog entries.

* Prevent restricted coins from ending up in the fee collector account. (#1846)

* [1845]: Update the marker SendRestrictionFn to not allow restricted coins to be sent to the fee collector account.

* [1845]: Add changelog entry.

* [1845]: Fix some exchange unit tests that broke because they were using restricted coins for the fees.

* [1845]: Update marker spec doc flowcharts.

* Bump cosmos-sdk to v0.46.13-pio-3 (from v0.46.13-pio-2). (#1848)

* Bump cosmos-sdk to v0.46.13-pio-3 (from v0.46.13-pio-2).

* Add changelog entry.
# Conflicts:
#	CHANGELOG.md
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