-
Notifications
You must be signed in to change notification settings - Fork 107
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(network): send height to peers #4904
Conversation
Codecov Report
@@ Coverage Diff @@
## main #4904 +/- ##
==========================================
- Coverage 79.18% 79.03% -0.16%
==========================================
Files 309 309
Lines 38783 38786 +3
==========================================
- Hits 30710 30654 -56
- Misses 8073 8132 +59 |
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.
Looks great!
It seems like syncing is slow enough to fail CI, but I don't think that's because of the changes in this PR. But we'll need to fix the sync bugs before we merge any more PRs.
I'll try re-running those jobs, in case it was temporary network slowness.
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.
We can merge this as soon as we fix the unrelated sync failures.
You could try:
|
@Mergifyio update |
✅ Branch has been successfully updated |
It seems like Zebra appears in block explorers and nodes without this fix, so I'm reducing the priority to make room for other PRs in the queue. |
@Mergifyio update |
✅ Branch has been successfully updated |
@Mergifyio update |
✅ Branch has been successfully updated |
Motivation
Zebra currently send height 0 in the
start_height
field of theMessage::Version
. This works protocol wise but DNS seeders expect a height here to classify peers. Resolves #4875Solution
Pretty simple solution, we already have everything available to end the height when we are building the version message.
Review
Anyone can review, i could be missing something as i thought this were going to be more complex. Local tests pass and i know this works while checkpointing, however i need to check a full sync. I expect the CI will assist me there.
Reviewer Checklist