-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
#10036 Replace codename Merge with Bellatrix (1st step) #10044
#10036 Replace codename Merge with Bellatrix (1st step) #10044
Conversation
It is not passing in my local system the test The tests I am running is |
|
Hey @leolara , you still need to run
|
@rkapka thank you for reminding me that. This PR is marked as WIP. The merge of develop into has caused me so git problems with a commit I did at the same time |
406f57d
to
d55d1c5
Compare
There are lots of things to rename, I will let you know when I think I am finished, so we can review @rkapka . I will try to also rebase on develop after that so it is fresher. Is there a bazel way of running gofmt? Or I just run it normally? |
You can run it normally or even as a pre commit hook. I recommend you mark the PR as draft, since then reviewers will get an automated email when you mark it requesting a review |
Thanks, I changed it to draft |
I want to note that there is more than a thousand "merge" string instances in the code, and that some times it actually means the action of merge, as opposed to the hard-fork. So I have to read it 🤣 |
If it makes it easier, you don't have to replace everything at once. Open a PR package by package is perfectly fine |
@@ -12,7 +12,7 @@ import ( | |||
"github.com/prysmaticlabs/prysm/testing/util" | |||
) | |||
|
|||
func Test_MergeComplete(t *testing.T) { | |||
func Test_BellatrixComplete(t *testing.T) { |
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.
This refers to the action of merge
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 @terencechain , this one slipped :-)
I am doing it more subject by subject, like I am now changing comments and will send that as a commit. If you think the PR is going to get too long to review, then I could do it in several PRs. I think I am kind of half way |
69a793a
to
30ff158
Compare
In order to do not make the review too tedious and complicated, I have decided to stop considering it WIP, get it reviewed and merged, and then I will continue with a follow up PR with the rest of the renaming. I have rebased on develop, no need to merge develop now. Please review @terencechain or other :-) |
@@ -33,7 +33,7 @@ message GenericSignedBeaconBlock { | |||
// Representing a signed, post-Altair fork beacon block. | |||
SignedBeaconBlockAltair altair = 2; | |||
|
|||
// Representing a signed, post-Merge fork beacon block. | |||
// Representing a signed, post-Bellatrix fork beacon block. | |||
SignedBeaconBlockMerge merge = 3; |
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.
SignedBeaconBlockMerge merge = 3; | |
SignedBeaconBlockBellatrix bellatrix = 3; |
Just a reminder here so we don't forget. We can do this in a follow-up PR
30ff158
to
74689bf
Compare
@terencechain I rebased to fix conflict, it seems it needs further action from mantainers to merge |
@@ -1073,7 +1073,7 @@ func (x *SyncAggregatorSelectionData) GetSubcommitteeIndex() uint64 { | |||
return 0 | |||
} | |||
|
|||
type BeaconStateMerge struct { | |||
type BeaconStateBellatrix struct { |
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.
Renaming in the generated code is not ideal. Please re-run ./hack/update-go-pbs.sh
after modifying proto files.
The reason is that file_proto_prysm_v1alpha1_beacon_state_proto_rawDesc
attribute should be updated as well and it's some hex bytes so rebuilding the pb.go files is really the only way to do it. You may need to run gofmt or goimports to sort the imports for the linter.
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.
ok
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.
Done, many files regenerated and pushed
e7c9fbe
to
435c709
Compare
@prestonvanloon @terencechain @rkapka I think all comments done, rebased to resolve conflicts. Do you want me to squash when merging or merge normally? Please, I think we need to move this, as this touches so many files many PRs will conflict this one |
It seems the problems are not only conflicts with new additions, but also the use of symbols I have renamed in other PRs. For example, I renamed version.Merge to version.Bellatrix, if someone uses version.Merge and merges a PR, then that symbol does not exist in my PR. I think we should freeze merging other PRs until this is merged or it will be very difficult |
@leolara You need to run gofmt and goimports after regenerating protofiles.
Git/Github is not letting me push to your branch. Please fix and we can merge quickly. |
Ok |
@prestonvanloon I ran those commands, but there were no effect, it seems my branch is clean or the problem is other |
@prestonvanloon I changed a setting try to push to my branch now |
* Rename BeaconStateMerge to BeaconStateBellatrix * Rename version.Merge to version.Bellatrix * Rename ComputeFieldRootsWithHasherMerge to ComputeFieldRootsWithHasherBellatrix * Rename test names to Bellatrix * Rename comments and strings to Bellatrix * Fix formatting in a few files * Revert wrong renaming in test name * Revert renaming to Bellatrix in mainnet_config.go * Revert renaming of db key without migration * Regenerate from proto changes * Rename new use of already renamed symbols * gofmt and goimports after regenerating protofiles * revert weird imports Co-authored-by: prestonvanloon <preston@prysmaticlabs.com> (cherry picked from commit b1c2454) # Conflicts: # beacon-chain/cache/sync_committee_head_state.go # beacon-chain/core/execution/upgrade.go # beacon-chain/state-proto/v3/state_trie.go
What type of PR is this?
Refactoring
What does this PR do? Why is it needed?
Replace codename Merge with Bellatrix
Which issues(s) does this PR fix?
Fixes #10036
Other notes for review
It does not complete 100% the task #10036 another PR will be necessary