AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 15 Bitcoin

pytest: fix broken test_pay_bolt11_metadata

Public commit record

What the developer wrote

Authored by Rusty Russell

58/100 · Thin
pytest: fix broken test_pay_bolt11_metadata

It uses a canned, but now expired invoice. Instead, use bolt11-cli to add metadata to
an existing invoice.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
✓ Descriptive subject✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit fixes a failing test in the Core Lightning test suite. The test previously relied on a hard-coded invoice that has now expired, causing automated tests to fail. The update dynamically generates a fresh invoice and adds payment metadata using a developer tool. There is no security vulnerability or product code change here—only a test maintenance fix.

Recommended action

No security action needed. This is a routine test fix. Reviewers may optionally verify that the new test still exercises the intended payment_metadata rejection path and that the hard-coded private key is only used in a regtest/dev environment.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 15/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 0/15
Confidence 10/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.