-
Notifications
You must be signed in to change notification settings - Fork 294
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!: rename qgb to blobstream #2639
Conversation
|
||
import "gogoproto/gogo.proto"; | ||
import "cosmos_proto/cosmos.proto"; | ||
import "google/api/annotations.proto"; | ||
|
||
option go_package = "github.com/celestiaorg/celestia-app/x/qgb/types"; | ||
option go_package = "github.com/celestiaorg/celestia-app/x/blobstream/types"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[note to reviewers]
This is API breaking
package celestia.qgb.v1; | ||
package celestia.blobstream.v1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since this is consensus breaking, we should not backport this change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why? we don't want to include the API breaking change in v1? I think it's okey as it won't require any hardspoon or so, just update the binary, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the path is included in the msg name, so changes this will result in different bytes included in any transactions or state. nodes with this change will know how to parse these txs, where nodes without the change will not
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
therefore this can only be included in v2. It will also require a migration script, which I think we should include in this change. That likely means waiting for the upgrade and e2e code to be finished so that we can properly test it.
Recall our conversaions about not being able to change the name of the qgb in the code before mainnet
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so changes this will result in different bytes included in any transactions or state. nodes with this change will know how to parse these txs, where nodes without the change will not
This provided people are sending register evm address transactions on mocha, which I assume is not the case. If not, then I can revert the tx related changes and only leave the query ones.
For the store, I kept the same keys so it shouldn't be a problem.
Codecov Report
@@ Coverage Diff @@
## main #2639 +/- ##
=======================================
Coverage 21.11% 21.11%
=======================================
Files 138 138
Lines 15767 15767
=======================================
Hits 3329 3329
Misses 12115 12115
Partials 323 323
|
I will update this PR not to include any consensus breaking change, so that we can merge it. cc @evan-forbes |
# Conflicts: # cmd/celestia-appd/cmd/root.go # test/util/testnode/full_node.go # x/blobstream/handler.go # x/blobstream/types/query.pb.go
Co-authored-by: Josh Stein <[email protected]>
Co-authored-by: Sanaz Taheri <[email protected]>
Co-authored-by: Josh Stein <[email protected]>
Co-authored-by: Josh Stein <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Can we add a quick note in the README.md
that this was formerly known as the qgb module (just for posterity)
We're planning to write a short ADR documenting this, and this we can maybe add a small section in the README referencing the ADR. |
<!-- Please read and fill out this form before submitting your PR. Please make sure you have reviewed our contributors guide before submitting your first PR. --> ## Overview The dependencies part of #2639 ## Checklist <!-- Please complete the checklist to ensure that the PR is ready to be reviewed. IMPORTANT: PRs should be left in Draft until the below checklist is completed. --> - [ ] New and updated code has appropriate documentation - [ ] New and updated code has new and/or updated testing - [ ] Required CI checks are passing - [ ] Visual proof for any user facing features like CLI or documentation updates - [ ] Linked issues closed with keywords
<!-- Please read and fill out this form before submitting your PR. Please make sure you have reviewed our contributors guide before submitting your first PR. --> ## Overview The dependencies part of #2639 ## Checklist <!-- Please complete the checklist to ensure that the PR is ready to be reviewed. IMPORTANT: PRs should be left in Draft until the below checklist is completed. --> - [ ] New and updated code has appropriate documentation - [ ] New and updated code has new and/or updated testing - [ ] Required CI checks are passing - [ ] Visual proof for any user facing features like CLI or documentation updates - [ ] Linked issues closed with keywords (cherry picked from commit c517bd2) # Conflicts: # go.mod # x/qgb/client/verify.go
<!-- Please read and fill out this form before submitting your PR. Please make sure you have reviewed our contributors guide before submitting your first PR. --> ## Overview The dependencies part of celestiaorg/celestia-app#2639 ## Checklist <!-- Please complete the checklist to ensure that the PR is ready to be reviewed. IMPORTANT: PRs should be left in Draft until the below checklist is completed. --> - [ ] New and updated code has appropriate documentation - [ ] New and updated code has new and/or updated testing - [ ] Required CI checks are passing - [ ] Visual proof for any user facing features like CLI or documentation updates - [ ] Linked issues closed with keywords
Overview
Closes #2613
Checklist