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

Bitcoin 0.12 misc P2P/Net PRs #4994

Merged
merged 9 commits into from Feb 19, 2021
Merged

Bitcoin 0.12 misc P2P/Net PRs #4994

merged 9 commits into from Feb 19, 2021

Conversation

Krellan and others added 9 commits February 18, 2021 19:03
Zcash: Was "Added -whiteconnections=<n> option" from bitcoin/bitcoin#5288. The
option was later removed in bitcoin/bitcoin#6374 which we merged in zcash#1258. This
commit contains the difference between the two.
The "please check your computer's data and time" message when the clock
deviates from the network currently generates an overkill of messages:

    orion@lethe:~/bitcoin$ src/bitcoind
    Warning: Warning: Please check that your computer's date and time are correct! If your clock is wrong Bitcoin Core will not work properly.

In the log:

    2015-09-27 16:24:13 *** Warning: Please check that your computer's date and time are correct! If your clock is wrong Bitcoin Core will not work properly.
    2015-09-27 16:24:13 Warning: Warning: Please check that your computer's date and time are correct! If your clock is wrong Bitcoin Core will not work properly.

Remove one level of 'Warning:' and reduce to one log message.
Add a comment that explains why the initial "getheader" requests are
made starting from the block preceding the currently best one.

Thanks to sdaftuar for the explanation!
Process `getheaders` messages from whitelisted peers even if we are in
initial block download. Whitelisted peers can always use a node as a
block source.

Also log a debug message when the request is ignored, for
troubleshooting.

Fixes #6971.
Mempool requests use a fair amount of bandwidth when the mempool is large,
 disconnecting peers using them follows the same logic as disconnecting
 peers fetching historical blocks.
@str4d str4d added C-upstream-port Category: Changes that are ported from the Bitcoin Core codebase. A-networking Area: Networking code labels Feb 18, 2021
This was referenced Feb 18, 2021
@str4d str4d added this to the Core Sprint 2021-06 milestone Feb 18, 2021
@nuttycom
Copy link
Contributor

@zkbot r+

@zkbot
Copy link
Contributor

zkbot commented Feb 18, 2021

📌 Commit 39cb786 has been approved by nuttycom

@zkbot
Copy link
Contributor

zkbot commented Feb 18, 2021

⌛ Testing commit 39cb786 with merge e10008da668b5d2dd026fcf7e1caf9b5cc8ee38d...

@zkbot
Copy link
Contributor

zkbot commented Feb 19, 2021

💔 Test failed - pr-merge

@str4d
Copy link
Contributor Author

str4d commented Feb 19, 2021

Transient CI failure.

@zkbot retry

@zkbot
Copy link
Contributor

zkbot commented Feb 19, 2021

⌛ Testing commit 39cb786 with merge 777deea2647a5ab420e619002274b2bca523a86a...

@zkbot
Copy link
Contributor

zkbot commented Feb 19, 2021

💔 Test failed - pr-merge

@str4d
Copy link
Contributor Author

str4d commented Feb 19, 2021

@zkbot retry

@zkbot
Copy link
Contributor

zkbot commented Feb 19, 2021

⌛ Testing commit 39cb786 with merge b62e35d...

@zkbot
Copy link
Contributor

zkbot commented Feb 19, 2021

☀️ Test successful - pr-merge
Approved by: nuttycom
Pushing b62e35d to master...

@zkbot zkbot merged commit b62e35d into zcash:master Feb 19, 2021
@str4d str4d deleted the 2074-net-misc-1 branch February 19, 2021 18:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-networking Area: Networking code C-upstream-port Category: Changes that are ported from the Bitcoin Core codebase.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants