-
Notifications
You must be signed in to change notification settings - Fork 904
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI Complaint about spend_tag in test_onchain_their_unilateral_out[True] #7526
Comments
niftynei
added a commit
to niftynei/lightning
that referenced
this issue
Aug 20, 2024
We were seeing occassional spends of commitment tx utxos in anchorspend txs, which was causing occasional test fails. We shouldn't be sending anchorspends at all for onchain funding-spends. The logic is in place for this, but the ordering of the state update to channel was incorrect, which lead to loglines as follows (we'd expect to see failure in ONCHAIN not NORMAL), given that the reason=onchain... "Peer permanent failure in CHANNELD_NORMAL: Funding transaction spent (reason=onchain)" A quick reordering of the state change + firing of `drop_to_chain` fixes the issue of sending the anchorspend tx, which removes the race case of onchaind adding utxos from the commitment tx to the utxoset, where the anchorspend construction was picking them up. Fixes ElementsProject#7526
niftynei
added a commit
to niftynei/lightning
that referenced
this issue
Aug 20, 2024
We were seeing occassional spends of commitment tx utxos in anchorspend txs, which was causing occasional test fails. We shouldn't be sending anchorspends at all for onchain funding-spends. The logic is in place for this, but the ordering of the state update to channel was incorrect, which lead to loglines as follows (we'd expect to see failure in ONCHAIN not NORMAL), given that the reason=onchain... "Peer permanent failure in CHANNELD_NORMAL: Funding transaction spent (reason=onchain)" A quick reordering of the state change + firing of `drop_to_chain` fixes the issue of sending the anchorspend tx, which removes the race case of onchaind adding utxos from the commitment tx to the utxoset, where the anchorspend construction was picking them up. Fixes ElementsProject#7526
rustyrussell
pushed a commit
to niftynei/lightning
that referenced
this issue
Sep 20, 2024
We were seeing occassional spends of commitment tx utxos in anchorspend txs, which was causing occasional test fails. We shouldn't be sending anchorspends at all for onchain funding-spends. The logic is in place for this, but the ordering of the state update to channel was incorrect, which lead to loglines as follows (we'd expect to see failure in ONCHAIN not NORMAL), given that the reason=onchain... "Peer permanent failure in CHANNELD_NORMAL: Funding transaction spent (reason=onchain)" A quick reordering of the state change + firing of `drop_to_chain` fixes the issue of sending the anchorspend tx, which removes the race case of onchaind adding utxos from the commitment tx to the utxoset, where the anchorspend construction was picking them up. Fixes ElementsProject#7526
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From splicing tests:
job-logs.txt
The text was updated successfully, but these errors were encountered: