Repository navigation
Use CollectionLength for the persisted event queue length #1145
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
cryptokvc
wants to merge
1
commit into
lightningdevkit:main
Choose a base branch
from
cryptokvc:patch-1
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.
Open
Changes from all commits
Commits
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
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.
Can you comment on why this is useful? If the data is there, we will read all the entries, and hence costly re-allocate?
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.
It's only there for a corrupted or truncated store. With the old
u16count the worst case was 65,535 slots, butCollectionLengthcan decode to anyu64, so a bad length would makewith_capacityabort the process before the first event read fails with aDecodeError. TheVecreaders inlightning::util::serbound it the same way (min(len, MAX_BUF_SIZE / size_of::<T>())). For a valid queue longer than the cap it only costs the usual amortized growth. Happy to switch to thatMAX_BUF_SIZEform to match LDK, or to drop the cap if you'd rather keep it simple.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.
Hmm, the thing is if we encounter corrupted data here there is no way to recover anyways. I guess we can bound to the minimum of actual len and
u16::MAX, or just leave it out. In general, we don't expect users to ever hit an event queue of 1024 events (in fact if they do, that's very bad), but if they ever did adding additional re-allocations on top is probably not great.