Skip to content

feat(p2p): only say the peer is "blocked" when explicitly configured#230

Merged
jansegre merged 1 commit intodevfrom
feat/adjustable-whitelist-warning
Jun 18, 2021
Merged

feat(p2p): only say the peer is "blocked" when explicitly configured#230
jansegre merged 1 commit intodevfrom
feat/adjustable-whitelist-warning

Conversation

@jansegre
Copy link
Member

This change makes it so we have to explicitly enable "peer blocked" warnings. Which should make it so "internal nodes" that don't use the default whitelist don't annoy everyone.

@jansegre jansegre self-assigned this Jun 11, 2021
@jansegre jansegre force-pushed the feat/adjustable-whitelist-warning branch from 92a30d2 to 9f2ef7d Compare June 11, 2021 08:51
@codecov-commenter
Copy link

codecov-commenter commented Jun 11, 2021

Codecov Report

Merging #230 (b6ad701) into dev (b2cf4d8) will decrease coverage by 0.01%.
The diff coverage is 25.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##              dev     #230      +/-   ##
==========================================
- Coverage   83.01%   82.99%   -0.02%     
==========================================
  Files         146      146              
  Lines       13575    13578       +3     
  Branches     1913     1914       +1     
==========================================
  Hits        11269    11269              
- Misses       1909     1913       +4     
+ Partials      397      396       -1     
Impacted Files Coverage Δ
hathor/p2p/states/peer_id.py 69.86% <0.00%> (-1.97%) ⬇️
hathor/conf/settings.py 100.00% <100.00%> (ø)
hathor/wallet/resources/thin_wallet/send_tokens.py 68.27% <0.00%> (-0.69%) ⬇️
hathor/transaction/base_transaction.py 92.66% <0.00%> (-0.32%) ⬇️
hathor/consensus.py 93.95% <0.00%> (+0.38%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b2cf4d8...b6ad701. Read the comment docs.

Copy link
Member

Choose a reason for hiding this comment

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

This warning is only in the case of a whitelist rejection, right? Maybe we should make this explicit in the comment or in the var name

Copy link
Member Author

Choose a reason for hiding this comment

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

What about WHITELIST_WARN_BLOCKED_PEERS?

@jansegre jansegre force-pushed the feat/adjustable-whitelist-warning branch 2 times, most recently from 8c30db3 to 084fbd3 Compare June 17, 2021 22:40
@jansegre jansegre force-pushed the feat/adjustable-whitelist-warning branch from 084fbd3 to b6ad701 Compare June 18, 2021 02:15
@jansegre jansegre merged commit dc244de into dev Jun 18, 2021
@jansegre jansegre deleted the feat/adjustable-whitelist-warning branch June 18, 2021 02:25
@jansegre jansegre mentioned this pull request Jun 23, 2021
glevco added a commit that referenced this pull request May 26, 2025
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.

4 participants