Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
  • 哪里不对？
#9,599 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

@vincenzopalazzo 已经在做这个了。

开始于 2026年10月7日。

  • #9605 来自 @vincenzopalazzo —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
52/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
c
领域
distributed-systems

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
C
星标
3.1k
派生
1k
平均合并
3 天 10 小时
30 天内合并 PR
40

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

ElementsProject/lightning 的其他 Issue

查看 ElementsProject/lightning 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。