Repository navigation
fix(liquidity): update LspNode in place on re-add #1147
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
Open
Bartok9
wants to merge
4
commits into
lightningdevkit:main
Choose a base branch
from
Bartok9:fix/ldp-liquidity-lsp-in-place-update
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+156
−34
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
a08c5f7
fix(liquidity): update LspNode in place on re-add
Bartok9 3be1fb5
fix(liquidity): apply token/0conf updates when LSP address is unchanged
Bartok9 46f911f
fix(liquidity): keep LSP protocols during reconnect
Bartok9 4963c4e
fix(liquidity): reconnect on LSP address change and generation-guard …
Bartok9 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, the
take()removal (L192-194) resolves the JIT-window concern.One thing still open: the snapshot rollback can race with a concurrent update for the same
node_id. The lock is released at L205, thencleanup(L209-221) restores the snapshot taken at L195:supported_protocols) over B's in-flight addr2Ok(()), but the stored config is addr0Suggested fix: serialize updates per LSP (lock held across the whole call), or connect + discover first and commit to
lsp_nodesonly on success, which makes rollback unnecessary. If concurrent re-adds aren't a supported use, a doc note would also be acceptable.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch — the lock is dropped before connect/discover, so a failed older update could write its snapshot over a newer re-add.
0499288 stamps each write with
config_generation. Cleanup restores the snapshot (or removes a fresh insert) only when that generation is still current; a later add for the samenode_idis left alone. Combined with the disconnect-then-dial fix so an address change actually hits the new endpoint before we treat the update as committed.