protofsm: update GR Manager usage and start using structured logging by ellemouton · Pull Request #9342 · lightningnetwork/lnd

ellemouton · 2024-12-10T05:46:08Z

This PR touches the protofsm package for 2 reasons:

update to use the latest GoroutineManager API introduced in: fn: Remove ctx from GoroutineManager constructor #9341
Update the StateMachine to thread a context through and to take a context via its API methods where it makes sense. With this update, logging can also be switched to the new structured logging pattern which allows us to avoid having to specify the FSM(%V) string for each log line

Depends on: btcsuite/btclog#20

coderabbitai · 2024-12-10T05:46:15Z

Important

Review skipped

Auto reviews are limited to specific labels.

🏷️ Labels to auto review (1)

llm-review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

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?

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

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)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

go.mod

protofsm/state_machine.go

Roasbeef · 2024-12-10T10:02:58Z

protofsm/state_machine.go

 	// TODO(roasbeef): could abstract further?
 	RegisterConfirmationsNtfn(txid *chainhash.Hash, pkScript []byte,
 		numConfs, heightHint uint32,
-		opts ...chainntnfs.NotifierOption,


Prob the main stylistic diff in the codebase rn, but I prefer this option as it makes it clearer where the args end, and the return value starts.

Imo that only holds if the return values can in-fact fit on one line which is not always the case.
Personally I find the ) { on the unindented line strange

Roasbeef · 2024-12-10T10:03:57Z

protofsm/state_machine.go

-				daemonEvent.TargetPeer.SerializeCompressed(),
-				lnutils.SpewLogClosure(daemonEvent.Msgs),
-			)
+			log.DebugS(ctx, "Sending message",


Do you have a print sample of the before and after here re formatting?

2024-12-10 13:20:44.552 [DBG]: FSM(test) Starting state machine 2024-12-10 13:20:44.552 [DBG]: FSM(test) Sending event event=(*protofsm.emitInternal)(0x1045f1240)({ }) 2024-12-10 13:20:44.552 [DBG]: FSM(test) Applying new event event=(*protofsm.emitInternal)(0x1045f1240)({ }) 2024-12-10 13:20:44.552 [DBG]: FSM(test) Processing event event=(*protofsm.emitInternal)(0x1045f1240)({ }) 2024-12-10 13:20:44.552 [DBG]: FSM(test) Adding new internal event to queue event !BADKEY=(*protofsm.goToFin)(0x1045f1240)({ }) 2024-12-10 13:20:44.552 [INF]: FSM(test) State transition from_state=*protofsm.dummyStateStart to_state=*protofsm.dummyStateStart 2024-12-10 13:20:44.552 [DBG]: FSM(test) Processing event event=(*protofsm.goToFin)(0x1045f1240)({ }) 2024-12-10 13:20:44.552 [INF]: FSM(test) State transition from_state=*protofsm.dummyStateStart to_state=*protofsm.dummyStateFin

Roasbeef · 2024-12-10T10:04:57Z

protofsm/state_machine.go

-					log.Debugf("FSM(%v): processing "+
-						"daemon %v daemon events",
-						s.cfg.Env.Name(), len(dEvents))
+					log.DebugS(ctx, "Processing daemon events",


Is this upper case construct something new we're attempting to make standard with the new logging format?

I think in general we go for log lines that start with upper case? searching around the code base, i can see that most of our log lines start with an upper case letter

Roasbeef · 2024-12-10T10:06:00Z

protofsm/state_machine.go

+	ctx context.Context) context.Context {
+
+	return btclog.WithCtx(ctx,
+		btclog.Fmt("fsm_name", s.cfg.Env.Name())) //nolint:govet


Is there anyway we can keep the old prefix nature? At least when scanning, IMO it's useful for it to be at the very start as depending on the size of your editor/viewport, the end of the line may require moving the cursor to actually view.

as the library stands today, no. But what can be done is: to create a prefixed logger in NewStateMachine and then carry that around in the StateMachine struct. Then we just need to remember to do s.log.* for log lines.

shall we do that instead here?

ok i've added a temporary commit at the end that does it this way. Let me know if you think this is ok and i can squash in the change.

The logs now look like this:

2024-12-10 13:20:44.552 [DBG]: FSM(test) Starting state machine 2024-12-10 13:20:44.552 [DBG]: FSM(test) Sending event event=(*protofsm.emitInternal)(0x1045f1240)({ }) 2024-12-10 13:20:44.552 [DBG]: FSM(test) Applying new event event=(*protofsm.emitInternal)(0x1045f1240)({ }) 2024-12-10 13:20:44.552 [DBG]: FSM(test) Processing event event=(*protofsm.emitInternal)(0x1045f1240)({ }) 2024-12-10 13:20:44.552 [DBG]: FSM(test) Adding new internal event to queue event !BADKEY=(*protofsm.goToFin)(0x1045f1240)({ }) 2024-12-10 13:20:44.552 [INF]: FSM(test) State transition from_state=*protofsm.dummyStateStart to_state=*protofsm.dummyStateStart 2024-12-10 13:20:44.552 [DBG]: FSM(test) Processing event event=(*protofsm.goToFin)(0x1045f1240)({ }) 2024-12-10 13:20:44.552 [INF]: FSM(test) State transition from_state=*protofsm.dummyStateStart to_state=*protofsm.dummyStateFin

squashed in the temp commit

ellemouton

Thanks for taking a look @Roasbeef - responded to your comments

protofsm/state_machine.go

ellemouton · 2024-12-10T10:12:21Z

protofsm/state_machine.go

-					log.Debugf("FSM(%v): processing "+
-						"daemon %v daemon events",
-						s.cfg.Env.Name(), len(dEvents))
+					log.DebugS(ctx, "Processing daemon events",


I think in general we go for log lines that start with upper case? searching around the code base, i can see that most of our log lines start with an upper case letter

ellemouton · 2024-12-10T10:13:59Z

protofsm/state_machine.go

+	ctx context.Context) context.Context {
+
+	return btclog.WithCtx(ctx,
+		btclog.Fmt("fsm_name", s.cfg.Env.Name())) //nolint:govet


as the library stands today, no. But what can be done is: to create a prefixed logger in NewStateMachine and then carry that around in the StateMachine struct. Then we just need to remember to do s.log.* for log lines.

shall we do that instead here?

ellemouton

squashed in the prefixed logging change & also added the commit for using a pointer to the GM instead as discussed @Roasbeef. PTAL 🙏

build/version.go

Roasbeef

LGTM 🩴

Roasbeef · 2024-12-18T13:40:36Z

protofsm/state_machine.go

 	return StateMachine[Event, Env]{
-		cfg:            cfg,
+		cfg: cfg,
+		log: log.WithPrefix(


bhandras

LGTM 🌮

bhandras · 2025-01-02T14:29:01Z

go.mod


 retract v0.0.2
+
+replace github.com/btcsuite/btclog/v2 => github.com/ellemouton/btclog/v2 v2.0.0-20241210110018-997ee6596623


nit: just flagging so it not forgotten :)

thanks yeah - luckily the linter wont ever let us forget these replaces :)

protofsm/state_machine.go

lightninglabs-deploy · 2025-01-10T09:04:24Z

@ellemouton, remember to re-request review from reviewers when ready

This bump includes a fix which prevents attribute value quoting if the value string contains a newline character. This is so that if we call spew.DumpS(), the output will stay nicely formatted. The update also includes a couple more Hex helpers which we can make use of now.

Update to use the latest version of the GoroutineManager which takes a context via the `Go` method instead of the constructor.

So that we dont have to remember to add the `FSM(%v)` prefix each time we write a log line.

ellemouton force-pushed the slogProtofsm branch from 8c9dad2 to 2fefda4 Compare December 10, 2024 08:32

Roasbeef requested changes Dec 10, 2024

View reviewed changes

ellemouton commented Dec 10, 2024

View reviewed changes

ellemouton force-pushed the slogProtofsm branch from 2fefda4 to a86da09 Compare December 10, 2024 11:15

ellemouton requested a review from Roasbeef December 10, 2024 11:23

ellemouton force-pushed the slogProtofsm branch 2 times, most recently from b0afb02 to d9194ed Compare December 12, 2024 08:02

ellemouton commented Dec 12, 2024

View reviewed changes

ellemouton mentioned this pull request Dec 12, 2024

fn: Remove ctx from GoroutineManager constructor #9341

Merged

ellemouton force-pushed the slogProtofsm branch from d9194ed to 2625e95 Compare December 12, 2024 09:08

guggero reviewed Dec 12, 2024

View reviewed changes

build/version.go Show resolved Hide resolved

saubyk requested a review from bhandras December 12, 2024 15:21

This was referenced Dec 13, 2024

htlcswitch+go.mod: use updated fn.ContextGuard #9344

Merged

htlcswitch: use fn.GoroutineManager #9140

Open

Roasbeef approved these changes Dec 18, 2024

View reviewed changes

ellemouton mentioned this pull request Jan 2, 2025

v2: add Hex helpers and dont quote values with newlines btcsuite/btclog#20

Merged

This was referenced Jan 2, 2025

Test context guard optimization #9401

Closed

fn: optimize context guard #9361

Merged

bhandras approved these changes Jan 2, 2025

View reviewed changes

ellemouton added 2 commits January 10, 2025 18:23

protofsm: use updated GoroutineManager API

b887c1c

Update to use the latest version of the GoroutineManager which takes a context via the `Go` method instead of the constructor.

ellemouton force-pushed the slogProtofsm branch from 2625e95 to c80651a Compare January 10, 2025 16:23

ellemouton added 3 commits January 10, 2025 18:25

protofsm: use prefixed logger for StateMachine

575ea7a

So that we dont have to remember to add the `FSM(%v)` prefix each time we write a log line.

protofsm: use structured logging

dfddeec

protofsm: use pointer to GoroutineManager

65c4c2c

ellemouton force-pushed the slogProtofsm branch from c80651a to 5de4278 Compare January 10, 2025 16:25

docs: add release notes entry

42ce9d6

ellemouton force-pushed the slogProtofsm branch from 5de4278 to 42ce9d6 Compare January 10, 2025 16:34

ellemouton merged commit 77848c4 into lightningnetwork:master Jan 10, 2025
30 of 35 checks passed

ellemouton deleted the slogProtofsm branch January 10, 2025 17:55


		retract v0.0.2

		replace github.com/btcsuite/btclog/v2 => github.com/ellemouton/btclog/v2 v2.0.0-20241210110018-997ee6596623

Conversation

ellemouton commented Dec 10, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai bot commented Dec 10, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ellemouton Dec 10, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ellemouton left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ellemouton left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Roasbeef left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

bhandras left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

lightninglabs-deploy commented Jan 10, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

ellemouton commented Dec 10, 2024 •

edited

Loading

coderabbitai bot commented Dec 10, 2024 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)

ellemouton Dec 10, 2024 •

edited

Loading