Detail LND's debug procedures.#9138
Conversation
|
Important Review skippedAuto reviews are limited to specific labels. 🏷️ Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
869bfd0 to
7c6d487
Compare
|
cc @Liongrass |
7c6d487 to
a2e6057
Compare
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
b0ca0d3 to
956b0f1
Compare
2618859 to
1ea9391
Compare
f17347f to
483a06b
Compare
a4d50ff to
ead2cea
Compare
7999da4 to
de6c5f2
Compare
de6c5f2 to
33406a0
Compare
|
@yyforyongyu: review reminder |
| The subsystem names are case-sensitive and must be all uppercase. | ||
|
|
||
| To identify the subsystems defined by an abbreviated name, you can search for | ||
| the abbrieviation in the [log.go](/log.go) file. Each subsystem |
There was a problem hiding this comment.
I think we can just do lncli debuglevel --show instead - doesn't need to visit the file?
There was a problem hiding this comment.
I described it because when I started, I really had no idea what the names really mean so I find it quite useful to mention how you can find the package which represent them.
Describe the basics of the LND profiler so that node runners can easily provide profile dumps to analyse faulty behaviour more quickly. Also update the description of LND's logging system.
During testing of this PR I figured out the the htlc interceptor was not shutdown and started properly in terms of closing the quit channel but also in terms of the relevant logs.
33406a0 to
cbd9f10
Compare
ziggie1984
left a comment
There was a problem hiding this comment.
Thanks a lot for this review @yyforyongyu ❤️
|
|
||
| // Initialize logging at the default logging level. | ||
| SetupLoggers(cfg.LogWriter, interceptor) | ||
|
|
There was a problem hiding this comment.
This is the fix, we need to first SetupLoggers, before we can print all the available ones.
We need to setup the loggers before we are able to show the complete list of available subsystems.
cbd9f10 to
f73504a
Compare
Uh oh!
There was an error while loading. Please reload this page.