Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat!: use versioned keys for dynamically adding and remove commit stores #3320
feat!: use versioned keys for dynamically adding and remove commit stores #3320
Changes from 10 commits
459012c
7822fb2
d2c9085
18df55f
7f71a8f
a5c535e
bea9815
46beef5
513245a
226d04f
50da483
18b1199
877864e
afa9097
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
[question][not blocking] out of curiosity, what was this param previously used for?
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.
I couldn't find any use of it in the code i.e. this was always true.
My theory is that you might want to start at an earlier height if you wanted to query the state at that height
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.
sounds good, agreed we should remove it then
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.
Ensure correct initialization of key maps in the
New
function.The initialization of
keys
,tkeys
, andmemKeys
usingsdk.NewKVStoreKeys
,sdk.NewTransientStoreKeys
, andsdk.NewMemoryStoreKeys
respectively, is critical. However, it's important to ensure that these functions are correctly populating the maps based on the current application version. This might require additional validation or error handling to ensure that the keys are correctly set up for the specified version.Check failure on line 691 in app/app.go
GitHub Actions / lint / golangci-lint
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.
Correct formatting issue.
The indentation here does not follow Go's conventional tab-based indentation. Correcting this will improve the readability and maintain the standard coding style.
Committable suggestion
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.
[optional] Here's a refactored implementation that I thought was easier to read. Defer to you if you want to include it:
with unit tests
Note: you'll have to convert the function signature back to using
fromVersion
/toVersion
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.
Thanks I definitely need to add the unit tests. It also reads easier and I don't think this is something that needs to be optimized so I will adopt your suggestion
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.
Ensure error handling in module migrations.
The
migrateModules
function is responsible for running module-specific migrations between versions. It's important to ensure robust error handling within this function to manage any issues that might arise during the migration process. Consider implementing comprehensive logging and error reporting mechanisms to aid in troubleshooting migration issues.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.
[not blocking][question] why is app version stored in the param store and consensus params? Is it stored anywhere else?
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.
No app version is only part of the consensus params in the param store. We load it in memory upon startup for easy reference.
I think the SDK ended up splitting out the param module which will likely be an annoying change to adopt
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.
[question] does this mean that to disable blobstream in v2, we have to do:
and
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.
[nit] it may be easier to read subsequent diffs if all the store keys were on new lines:
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.
Yup, I think that should be everything.
I wonder if we can even remove the directory and import "github.com/celestiaorg/celestia-app/x/blobstream"
I can list it out new lines
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.
Cool idea! I just checked and it looks like we may have to use the old name still b/c the last published release of celestia-app (v1.8.0) still calls it qgb: https://pkg.go.dev/github.com/celestiaorg/[email protected]/x/qgb