What the developer wrote
Authored by Gijs van Dam
chore: fix linter issues in brontide.go
Post merge of #10089, a linter issues was introduced in `brontide.go`.
This commit fixes that issue.
What changed, and why it matters
This is a trivial code cleanup commit that adds a blank line to satisfy a Go linter rule. It does not change program behavior, fix a bug, or address any security issue.
No action needed. This is a non-security style-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds a single blank line before a return statement inside peer/brontide.go in the handleLocalCloseReq function. The commit message explicitly states this is to fix a linter issue introduced after merging PR #10089. There are no functional changes.
Changed components
peer/brontide.goInspect captured patch +1 / −0
diff --git a/peer/brontide.go b/peer/brontide.go
index b1e8838..d624ac9 100644
--- a/peer/brontide.go
+++ b/peer/brontide.go
@@ -4335,6 +4335,7 @@ func (p *Brontide) handleLocalCloseReq(req *htlcswitch.ChanClose) {
"unknown", chanID)
p.log.Errorf(err.Error())
req.Err <- err
+
return
}
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.