Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

`splice_update` hangs and never returns, even after disconnecting peer

Aperta
  • Qualcosa non va?
#9,599 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@vincenzopalazzo ci sta già lavorando.

Dal 7/10/2026.

  • #9605 di @vincenzopalazzo — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c
Ambito
distributed-systems

Direzione di ricerca

Start by reproducing the reported createpsbt → utxoupdatepsbt → splice_init → splice_update sequence. Trace the splice_update handling around the logged WIRE_TX_ADD_INPUT and WIRE_TX_COMPLETE exchange; the issue does not name a file or test. Done means the RPC no longer hangs in this case, including after peer disconnection, and the behavior is covered by a regression test.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Maybe the I/O plumbing has a leak somewhere.

Here is what I did:

  1. I called Bitcoin Core's createpsbt to create a PSBT with three inputs and no outputs.
  2. I called Bitcoin Core's utxoupdatepsbt to populate the UTxO information for the inputs.
  3. I called CLN's splice_init, passing the channel_id, the relative_amount that I was proposing to add to the channel, the initialpsbt from utxoupdatepsbt, and feerate_per_kw=75. This returned a PSBT with my contributed three inputs plus the existing channel outpoint as a fourth input and also one output that would have become the new channel outpoint. (There was no change output because my relative_amount was exactly equal to the sum of my contributed input amounts minus the fee.)
  4. I called CLN's splice_update, passing the channel_id and the psbt from splice_init. This simply hanged and never returned.
  5. I tried forcibly disconnecting the peer, which worked, but the splice_update RPC still did not return.

The log contains:

2026-10-05T03:57:51.888Z DEBUG   03…ee-channeld-chan#256329: Getting handle_splice_init psbt version 2 (RBF?: n)
2026-10-05T03:57:51.888Z DEBUG   03…ee-channeld-chan#256329: Sending peer that we want to STFU.
2026-10-05T03:57:51.888Z DEBUG   03…ee-channeld-chan#256329: peer_out WIRE_STFU
2026-10-05T03:57:51.912Z DEBUG   03…ee-channeld-chan#256329: peer_in WIRE_STFU
2026-10-05T03:57:51.912Z DEBUG   03…ee-channeld-chan#256329: STFU initiator local.
2026-10-05T03:57:51.912Z UNUSUAL 03…ee-channeld-chan#256329: STFU complete: we are quiescent
2026-10-05T03:57:51.912Z UNUSUAL 03…ee-channeld-chan#256329: STFU complete: setting stfu_wait_single_msg = true
2026-10-05T03:57:51.912Z DEBUG   03…ee-channeld-chan#256329: peer_out WIRE_SPLICE
2026-10-05T03:57:51.946Z DEBUG   03…ee-channeld-chan#256329: peer_in WIRE_SPLICE_ACK
2026-10-05T03:57:51.946Z DEBUG   03…ee-channeld-chan#256329: Sending master 7208
2026-10-05T03:57:51.947Z DEBUG   03…ee-channeld-chan#256329: ... , awaiting 7209
2026-10-05T03:57:51.948Z DEBUG   03…ee-channeld-chan#256329: Got it!
2026-10-05T04:01:10.119Z DEBUG   03…ee-channeld-chan#256329: Sending master 7208
2026-10-05T04:01:10.135Z DEBUG   03…ee-channeld-chan#256329: ... , awaiting 7209
2026-10-05T04:01:10.136Z DEBUG   03…ee-channeld-chan#256329: Got it!
2026-10-05T04:01:10.136Z DEBUG   03…ee-channeld-chan#256329: ictx->shared_outpoint=a1…a9:8
2026-10-05T04:01:10.136Z DEBUG   03…ee-channeld-chan#256329: point=a1…a9:8
2026-10-05T04:01:10.136Z DEBUG   03…ee-channeld-chan#256329: Adding shared input 36…67
2026-10-05T04:01:10.136Z DEBUG   03…ee-channeld-chan#256329: peer_out WIRE_TX_ADD_INPUT
2026-10-05T04:01:10.160Z DEBUG   03…ee-channeld-chan#256329: peer_in WIRE_TX_COMPLETE

I'm not sure why the success log messages from the STFU exchange should be considered UNUSUAL. That looks wrong to me.

Anyway, we sent WIRE_TX_ADD_INPUT and received WIRE_TX_COMPLETE, and then we went on vacation. ☹️👎🏻

This was on CLN v26.06.8.

Lingua principale
C
Stelle
3.1k
Fork
1k
Merge medio
3g 10h
PR unite (30g)
40

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ElementsProject/lightning

Tutte le issue di ElementsProject/lightning

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.