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

Minimum changes for fixing 1.4.0 follow capabilities. #980

Merged
merged 1 commit into from
May 4, 2022

Conversation

AnomalRoil
Copy link
Member

The changes in #979 are too numerous and aren't playing nicely with some of our file handling, and regression tests, it will need more attention in the future.

This should fix our issues for now.

Copy link
Contributor

@mcamou mcamou left a comment

Choose a reason for hiding this comment

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

LGTM

@willscott
Copy link
Member

regression doesn't seem happy with this one either. have you looked into what it's unhappy with?

@AnomalRoil
Copy link
Member Author

@willscott Yeah, I think it's the hash chain changes which make it not compatible with previous v1.4.0 nodes. However it should be fine.

The problem is that the empty string "" wasn't hashed to compute the hash chain, but the "default" value was hashed, whereas neither should have been hashed if we want the default beaconID to keep the same hash chain value as the old way of computing it.

@AnomalRoil AnomalRoil merged commit 19b94a5 into master May 4, 2022
@AnomalRoil AnomalRoil deleted the fix/1.4.1 branch May 4, 2022 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants