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

fix(drs): fetch only relevant param on upgrade to avoid panic on new params #628

Merged
merged 3 commits into from
Dec 10, 2024

Conversation

srene
Copy link
Contributor

@srene srene commented Dec 10, 2024

Description


Closes #627

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.

PR review checkboxes:

I have...

  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Targeted PR against the correct branch
  • included the correct type prefix in the PR title
  • Linked to the GitHub issue with discussion and accepted design
  • Targets only one GitHub issue
  • Wrote unit and integration tests
  • Wrote relevant migration scripts if necessary
  • All CI checks have passed
  • Added relevant godoc comments
  • Add an issue in the e2e-tests repo if necessary

SDK Checklist

  • Import/Export Genesis
  • Registered Invariants
  • Registered Events
  • Updated openapi.yaml
  • No usage of go map
  • No usage of time.Now()
  • Used fixed point arithmetic and not float arithmetic
  • Avoid panicking in Begin/End block as much as possible
  • No unexpected math Overflow
  • Used sendCoin and not SendCoins
  • Out-of-block compute is bounded
  • No serialized ID at the end of store keys
  • UInt to byte conversion should use BigEndian

Full security checklist here


For Reviewer:

  • Confirmed the correct type prefix in the PR title
  • Reviewers assigned
  • Confirmed all author checklist items have been addressed

After reviewer approval:

  • In case the PR targets the main branch, PR should not be squash merge in order to keep meaningful git history.
  • In case the PR targets a release branch, PR must be rebased.

@srene srene requested a review from a team as a code owner December 10, 2024 12:38
@srene srene linked an issue Dec 10, 2024 that may be closed by this pull request
@srene srene self-assigned this Dec 10, 2024
@omritoptix omritoptix changed the title fix(drs upgrade): drs upgrade refactor to allow new params definition fix(drs): fetch only relevant param on upgrade to avoid panic on new params Dec 10, 2024
@omritoptix omritoptix merged commit 62fded9 into main Dec 10, 2024
5 of 7 checks passed
@omritoptix omritoptix deleted the srene/627-upgrade-drs-update branch December 10, 2024 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

forced drs upgrade (fork) not working when new rollapp params are defined
2 participants