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: chain: record heaviest tipset before notifying #10694

Merged
merged 1 commit into from
Apr 25, 2023

Conversation

Stebalien
Copy link
Member

Clearly this hasn't caused any issues, but I'm pretty sure we should be updating the current head before notifying about it.

Clearly this hasn't caused any issues, but I'm pretty sure we should be
updating the current head _before_ notifying about it.
@Stebalien Stebalien requested a review from a team as a code owner April 19, 2023 00:44
@Stebalien Stebalien requested a review from magik6k April 19, 2023 00:45
Copy link
Contributor

@magik6k magik6k left a comment

Choose a reason for hiding this comment

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

IDK if this change makes any practical difference, but I can see how it can feel slightly more correct.

@Stebalien Stebalien merged commit 7162c65 into master Apr 25, 2023
@Stebalien Stebalien deleted the steb/write-head-before-reorg branch April 25, 2023 18:56
@Stebalien
Copy link
Member Author

Yeah, it shouldn't make any practical difference. It just makes me nervous.

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

2 participants