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: do not allow the update of initialization parameters of launched chains and stop a chain from launching if #2245

Merged
merged 2 commits into from
Sep 10, 2024

Conversation

insumity
Copy link
Contributor

Description

This PR introduces 2 changes:

  • do not allow the update of initialization parameters of launched chains
  • stop an initialized chain from getting launched if a MsgUpdateConsumer is sent with initializationParameters.SpawnTime that is zero and move the chain back to the REGISTERED phase

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 the change is state-machine breaking
  • Confirmed this PR does not introduce changes requiring state migrations, OR migration code has been added to consumer and/or provider modules
  • Targeted the correct branch (see PR Targeting)
  • Provided a link to the relevant issue or specification
  • Followed the guidelines for building SDK modules
  • Included the necessary unit and integration tests
  • 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
  • If this PR is library API breaking, bump the go.mod version string of the repo, and follow through on a new major release

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 ! the type prefix if the change is state-machine breaking
  • confirmed this PR does not introduce changes requiring state migrations, OR confirmed migration code has been added to consumer and/or provider modules
  • 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

@github-actions github-actions bot added the C:x/provider Assigned automatically by the PR labeler label Sep 10, 2024
@insumity insumity marked this pull request as ready for review September 10, 2024 12:29
@insumity insumity requested a review from a team as a code owner September 10, 2024 12:29
Copy link
Contributor

@p-offtermatt p-offtermatt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. This means there is now a way to move back to Registered from Initialized, is there any place where we need the assumption that this cannot happen? I think that it is ok in principle.

Copy link
Contributor

@mpoke mpoke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

x/ccv/provider/keeper/msg_server.go Outdated Show resolved Hide resolved
@insumity insumity added this pull request to the merge queue Sep 10, 2024
Merged via the queue into main with commit 0600f7f Sep 10, 2024
14 of 15 checks passed
@insumity insumity deleted the insumity/small-fixes branch September 10, 2024 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C:x/provider Assigned automatically by the PR labeler
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants