This PR is to resolve issue 20576. It focuses on introducing different levels of net logging. As a starting point, as mentioned in the issue #20576 , it creates separate lower-frequency, important peer-level events (netpeers) from very high-frequency message-level passing (netmessages).
p2p: Split network logging into two categories #24247
pull anshu-khare-design wants to merge 0 commits into bitcoin:master from anshu-khare-design:issue_20576 changing 0 files +0 −0-
anshu-khare-design commented at 10:26 AM on February 3, 2022: none
- laanwj added the label Utils/log/libs on Feb 3, 2022
- laanwj renamed this:
Issue 20576
p2p: Split network logging into two categories
on Feb 3, 2022 - laanwj added the label P2P on Feb 3, 2022
-
brunoerg commented at 12:00 PM on February 3, 2022: member
Hi, @anshu-khare-design. Thanks for this. Some points:
- I think you might write a more appropriate commit message (maybe the same as the PR title)
- CI is failing because of
rpc_miscfunctional test:
# Test logging RPC returns the expected number of logging categories. assert_equal(len(node.logging()), 27)this assertion is failing because with this PR we have one more category, so, in total, 28. You should update this test as well.
- anshu-khare-design referenced this in commit f9f4d37fa2 on Feb 3, 2022
-
brunoerg commented at 4:59 PM on February 3, 2022: member
Cool. Now you should squash the commits. See: https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#squashing-commits
- anshu-khare-design referenced this in commit bbb9a973ab on Feb 4, 2022
-
anshu-khare-design commented at 12:19 AM on February 4, 2022: none
Oops.. I think I did something wrong.. I first wrote
$ git rebase -i HEAD~3 $ git pull origin issue_20576 (Since it was asking me to take a pull) $ git push origin issue_20576
-
ghost commented at 1:08 AM on February 4, 2022: none
@anshu-khare-design try this
git reset --hard 133f73e86bd7c3114263500be2fb5090dd76b4bc git push origin +133f73e86bd7c3114263500be2fb5090dd76b4bc^:issue_20576 git push origin 133f73e86bd7c3114263500be2fb5090dd76b4bc:issue_20576This will close the pull request, it will have 0 commits and you can start fresh in your fork repository
Make all the changes in the code, do 1 commit and reopen pull request.
-
DrahtBot commented at 3:55 AM on February 4, 2022: member
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Conflicts
Reviewers, this pull request conflicts with the following ones:
- #24230 (indexes: Stop using node internal types and locking cs_main, improve sync logic by ryanofsky)
- #24178 (p2p: Respond to getheaders if we have sufficient chainwork by sdaftuar)
- #24008 (assumeutxo: net_processing changes by jamesob)
- #23604 (Use Sock in CNode by vasild)
- #23443 (p2p: Erlay support signaling by naumenkogs)
- #22778 (net processing: Reduce resource usage for inbound block-relay-only connections by jnewbery)
- #22053 (refactor: Release cs_main before MaybeSendFeefilter by MarcoFalke)
- #21160 (net/net processing: Move tx inventory into net_processing by jnewbery)
- #20799 (net processing: Only support version 2 compact blocks by jnewbery)
- #20726 (p2p: Add DISABLETX message for negotiating block-relay-only connections by sdaftuar)
- #15606 (assumeutxo by jamesob)
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
- DrahtBot added the label Needs rebase on Feb 4, 2022
-
DrahtBot commented at 8:58 AM on February 4, 2022: member
<!--cf906140f33d8803c4a75a2196329ecb-->
🐙 This pull request conflicts with the target branch and needs rebase.
<sub>Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".</sub>
-
brunoerg commented at 1:56 PM on February 5, 2022: member
@prayank23 gave some tips. Feel free to ask for help whenever needed.
- anshu-khare-design closed this on Feb 5, 2022
- anshu-khare-design force-pushed on Feb 5, 2022
- anshu-khare-design referenced this in commit 0dba6126d5 on Feb 5, 2022
-
fanquake commented at 11:22 PM on February 6, 2022: member
Please don't open new PRs for the same change. (#24273).
- DrahtBot locked this on Feb 6, 2023