What changed, and why it matters
This commit only fixes blank-line spacing in a single test file to satisfy lint checks. It adds one blank line after a function signature and removes one trailing blank line. There are no code behavior changes, no bug fixes, and no security implications.
No security action needed. Treat as routine lint/style cleanup.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff in invoices/invoiceregistry_test.go is purely cosmetic: it inserts a blank line after the signature of testInvoiceRegistryProcessingErrors and deletes a trailing blank line at the end of testReplayedAMPHtlcNearExpiry. No executable logic, imports, dependencies, or interfaces changed.
Changed components
invoices/invoiceregistry_test.goInspect captured patch +1 / −1
### invoices/invoiceregistry_test.go
@@ -105,6 +105,7 @@ func newFaultTestContext(t *testing.T, cfg *invpkg.RegistryConfig,
// retryable and interceptor errors only fail HTLCs that are known to be new.
func testInvoiceRegistryProcessingErrors(t *testing.T,
makeDB func(t *testing.T) (invpkg.InvoiceDB, *clock.TestClock)) {
+
t.Run("ordinary payment uses one lookup", func(t *testing.T) {
ctx, faultDB := newFaultTestContext(t, nil, makeDB)
invoice := newInvoice(t, false, false)
@@ -1102,7 +1103,6 @@ func testReplayedAMPHtlcNearExpiry(t *testing.T,
)
require.NoError(t, err)
require.Nil(t, resolution)
-
}
// testReplayedHoldKeysendNearExpiry asserts that a held keysend HTLC that isWhy 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.