Skip to content

DRY up batched KVStore reads utility methods - #876

Merged
tnull merged 1 commit into
lightningdevkit:mainfrom
tnull:2026-04-batching-store
Apr 29, 2026
Merged

DRY up batched KVStore reads utility methods#876
tnull merged 1 commit into
lightningdevkit:mainfrom
tnull:2026-04-batching-store

Conversation

@tnull

@tnulltnull commented Apr 15, 2026•
edited
Loading

Copy link
Copy Markdown
Collaborator
DRY up batched KVStore reads with `read_all_objects` helper
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000

@tnull
tnull requested a review from joostjagerApril 15, 2026 13:54
@ldk-reviews-bot

ldk-reviews-bot commented Apr 15, 2026•
edited
Loading

Copy link
Copy Markdown

👋 Thanks for assigning @joostjager as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

@tnulltnull self-assigned this Apr 16, 2026
@tnulltnull moved this to Goal: Merge in Weekly GoalsApr 16, 2026
@ldk-reviews-bot

ldk-reviews-bot commented Apr 18, 2026

Copy link
Copy Markdown

🔔 1st Reminder

Hey @joostjager! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@ldk-reviews-bot

ldk-reviews-bot commented Apr 20, 2026

Copy link
Copy Markdown

🔔 2nd Reminder

Hey @joostjager! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@tnulltnull added this to the 0.8 milestone Apr 20, 2026
@Camillarhi

Camillarhi commented Apr 20, 2026

Copy link
Copy Markdown
Contributor

LGTM

@Camillarhi

Camillarhi commented Apr 21, 2026

Copy link
Copy Markdown
Contributor

This now needs a rebase, there's a merge conflict.

@ldk-reviews-bot

ldk-reviews-bot commented Apr 22, 2026

Copy link
Copy Markdown

🔔 3rd Reminder

Hey @joostjager! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

joostjager
joostjager reviewed Apr 22, 2026
View reviewed changes

@joostjagerjoostjager left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure a generic client-side read throttle is the right abstraction here.

I think the motivation is mainly VSS-specific? For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?

Comment threadsrc/builder.rs
Comment threadsrc/io/utils.rs Outdated
@tnull

tnull commented Apr 24, 2026

Copy link
Copy Markdown
CollaboratorAuthor

I am not sure a generic client-side read throttle is the right abstraction here.

Hmm, I tend to agree, though pre-existing.

I think the motivation is mainly VSS-specific?

Well, yes, presumably postgres could also benefit from it, though the store probably should switch to connection pooling anyways?

For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?

Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?

@tnull
tnull requested a review from joostjagerApril 27, 2026 08:19
@tnulltnull mentioned this pull request Apr 27, 2026
Open
joostjager
joostjager reviewed Apr 28, 2026
View reviewed changes

@joostjagerjoostjager left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?

I think this is a good move, and later expand either towards protocol-level multi reads for vss, or perhaps generalize for other backends if the need arises.

@tnull

tnull commented Apr 28, 2026

Copy link
Copy Markdown
CollaboratorAuthor

Discussed offline, decided we're not going with the BatchingStore abstraction right now, but only DRY up the read_ utility methods in io/utils.rs in this PR.

@tnulltnull changed the title DRY up batched KVStore reads with semaphore-based BatchingStoreDRY up batched KVStore reads utility methodsApr 28, 2026
@tnull
tnullforce-pushed the 2026-04-batching-store branch from 5b8cebf to 22866abCompareApril 28, 2026 09:39
@tnull
tnull requested a review from joostjagerApril 28, 2026 09:40
joostjager
joostjager previously approved these changes Apr 28, 2026
View reviewed changes

@joostjagerjoostjager left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, uncontentious. Rebase needed.

Comment threadsrc/io/utils.rs
@tnull
DRY up batched KVStore reads with read_all_objects helper
7aa48fa
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000
@tnull
tnullforce-pushed the 2026-04-batching-store branch from 22866ab to 7aa48faCompareApril 28, 2026 11:18
@tnull

tnull commented Apr 28, 2026

Copy link
Copy Markdown
CollaboratorAuthor

Looks good, uncontentious. Rebase needed.

Rebased, sorry, forgot about that before.

@tnull
tnull requested a review from joostjagerApril 28, 2026 11:19
@tnull
tnull merged commit a8e2e5f into lightningdevkit:mainApr 29, 2026
16 of 21 checks passed
@github-project-automationgithub-project-automationBot moved this from Goal: Merge to Done in Weekly GoalsApr 29, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@joostjagerjoostjagerjoostjager approved these changes

Assignees

@tnulltnull

Labels

None yet

Projects

Weekly Goals
Status: Done

Milestone

0.8

Development

Successfully merging this pull request may close these issues.

4 participants

@tnull@ldk-reviews-bot@Camillarhi@joostjager
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
DRY up batched `KVStore` reads utility methods by tnull · Pull Request #876 · lightningdevkit/ldk-node · GitHub
Skip to content
DRY up batched KVStore reads utility methods - #876
Merged
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Apr 29, 2026
Merged
DRY up batched KVStore reads utility methods#876
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Conversation
@tnull
@tnulltnull
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

Collaborator
DRY up batched KVStore reads with `read_all_objects` helper
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000

@tnull
tnull
requested a review
from joostjagerApril 15, 2026 13:54
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

👋 Thanks for assigning @joostjager as a reviewer!

I'll wait for their review and will help manage the review process.

Once they submit their review, I'll check if a second reviewer would be helpful.
@tnulltnull
self-assigned this
Apr 16, 2026
@tnulltnull
moved this to Goal: Merge
in Weekly GoalsApr 16, 2026
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 18, 2026

Copy link


Copy Markdown

🔔 1st Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 20, 2026

Copy link


Copy Markdown

🔔 2nd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@tnulltnull
added this to the 0.8 milestone
Apr 20, 2026
@Camillarhi
Camillarhi
commented
Apr 20, 2026

Copy link


Copy Markdown

Contributor
LGTM
@Camillarhi
Camillarhi
commented
Apr 21, 2026

Copy link


Copy Markdown

Contributor
This now needs a rebase, there's a merge conflict.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 22, 2026

Copy link


Copy Markdown

🔔 3rd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
joostjager
joostjager
reviewed
Apr 22, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure a generic client-side read throttle is the right abstraction here.
I think the motivation is mainly VSS-specific? For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Comment threadsrc/builder.rs
Comment threadsrc/io/utils.rs
Outdated

@tnull
tnull
commented
Apr 24, 2026

Copy link


Copy Markdown

CollaboratorAuthor
I am not sure a generic client-side read throttle is the right abstraction here.
Hmm, I tend to agree, though pre-existing.
I think the motivation is mainly VSS-specific?
Well, yes, presumably postgres could also benefit from it, though the store probably should switch to connection pooling anyways?
For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
@tnull
tnull
requested a review
from joostjagerApril 27, 2026 08:19
@tnulltnull
mentioned this pull request
Apr 27, 2026
 Open

joostjager
joostjager
reviewed
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
I think this is a good move, and later expand either towards protocol-level multi reads for vss, or perhaps generalize for other backends if the need arises.
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Discussed offline, decided we're not going with the BatchingStore abstraction right now, but only DRY up the read_ utility methods in io/utils.rs in this PR.
@tnulltnull
changed the title
DRY up batched KVStore reads with semaphore-based BatchingStoreDRY up batched KVStore reads utility methodsApr 28, 2026
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
5b8cebf to
22866abCompareApril 28, 2026 09:39
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 09:40
joostjager
joostjager
previously approved these changes
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, uncontentious. Rebase needed.
Comment threadsrc/io/utils.rs
@tnull
DRY up batched KVStore reads with read_all_objects helper
7aa48fa
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
22866ab to
7aa48faCompareApril 28, 2026 11:18
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Looks good, uncontentious. Rebase needed.
Rebased, sorry, forgot about that before.
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 11:19
@tnull
tnull
merged commit a8e2e5f
into
lightningdevkit:mainApr 29, 2026

16 of 21 checks passed

@github-project-automationgithub-project-automationBot
moved this from Goal: Merge
to Done
in Weekly GoalsApr 29, 2026
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@joostjagerjoostjagerjoostjager approved these changes

Assignees

@tnulltnull

Labels


None yet


Projects

Weekly Goals

Status: Done


Milestone

0.8

Development

Successfully merging this pull request may close these issues.

4 participants

@tnull@ldk-reviews-bot@Camillarhi@joostjager

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
DRY up batched `KVStore` reads utility methods by tnull · Pull Request #876 · lightningdevkit/ldk-node · GitHub
Skip to content
DRY up batched KVStore reads utility methods - #876
Merged
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Apr 29, 2026
Merged
DRY up batched KVStore reads utility methods#876
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Conversation
@tnull
@tnulltnull
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

Collaborator
DRY up batched KVStore reads with `read_all_objects` helper
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000

@tnull
tnull
requested a review
from joostjagerApril 15, 2026 13:54
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

👋 Thanks for assigning @joostjager as a reviewer!

I'll wait for their review and will help manage the review process.

Once they submit their review, I'll check if a second reviewer would be helpful.
@tnulltnull
self-assigned this
Apr 16, 2026
@tnulltnull
moved this to Goal: Merge
in Weekly GoalsApr 16, 2026
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 18, 2026

Copy link


Copy Markdown

🔔 1st Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 20, 2026

Copy link


Copy Markdown

🔔 2nd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@tnulltnull
added this to the 0.8 milestone
Apr 20, 2026
@Camillarhi
Camillarhi
commented
Apr 20, 2026

Copy link


Copy Markdown

Contributor
LGTM
@Camillarhi
Camillarhi
commented
Apr 21, 2026

Copy link


Copy Markdown

Contributor
This now needs a rebase, there's a merge conflict.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 22, 2026

Copy link


Copy Markdown

🔔 3rd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
joostjager
joostjager
reviewed
Apr 22, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure a generic client-side read throttle is the right abstraction here.
I think the motivation is mainly VSS-specific? For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Comment threadsrc/builder.rs
Comment threadsrc/io/utils.rs
Outdated

@tnull
tnull
commented
Apr 24, 2026

Copy link


Copy Markdown

CollaboratorAuthor
I am not sure a generic client-side read throttle is the right abstraction here.
Hmm, I tend to agree, though pre-existing.
I think the motivation is mainly VSS-specific?
Well, yes, presumably postgres could also benefit from it, though the store probably should switch to connection pooling anyways?
For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
@tnull
tnull
requested a review
from joostjagerApril 27, 2026 08:19
@tnulltnull
mentioned this pull request
Apr 27, 2026
 Open

joostjager
joostjager
reviewed
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
I think this is a good move, and later expand either towards protocol-level multi reads for vss, or perhaps generalize for other backends if the need arises.
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Discussed offline, decided we're not going with the BatchingStore abstraction right now, but only DRY up the read_ utility methods in io/utils.rs in this PR.
@tnulltnull
changed the title
DRY up batched KVStore reads with semaphore-based BatchingStoreDRY up batched KVStore reads utility methodsApr 28, 2026
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
5b8cebf to
22866abCompareApril 28, 2026 09:39
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 09:40
joostjager
joostjager
previously approved these changes
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, uncontentious. Rebase needed.
Comment threadsrc/io/utils.rs
@tnull
DRY up batched KVStore reads with read_all_objects helper
7aa48fa
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
22866ab to
7aa48faCompareApril 28, 2026 11:18
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Looks good, uncontentious. Rebase needed.
Rebased, sorry, forgot about that before.
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 11:19
@tnull
tnull
merged commit a8e2e5f
into
lightningdevkit:mainApr 29, 2026

16 of 21 checks passed

@github-project-automationgithub-project-automationBot
moved this from Goal: Merge
to Done
in Weekly GoalsApr 29, 2026
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@joostjagerjoostjagerjoostjager approved these changes

Assignees

@tnulltnull

Labels


None yet


Projects

Weekly Goals

Status: Done


Milestone

0.8

Development

Successfully merging this pull request may close these issues.

4 participants

@tnull@ldk-reviews-bot@Camillarhi@joostjager

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
DRY up batched `KVStore` reads utility methods by tnull · Pull Request #876 · lightningdevkit/ldk-node · GitHub
Skip to content
DRY up batched KVStore reads utility methods - #876
Merged
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Apr 29, 2026
Merged
DRY up batched KVStore reads utility methods#876
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Conversation
@tnull
@tnulltnull
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

Collaborator
DRY up batched KVStore reads with `read_all_objects` helper
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000

@tnull
tnull
requested a review
from joostjagerApril 15, 2026 13:54
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

👋 Thanks for assigning @joostjager as a reviewer!

I'll wait for their review and will help manage the review process.

Once they submit their review, I'll check if a second reviewer would be helpful.
@tnulltnull
self-assigned this
Apr 16, 2026
@tnulltnull
moved this to Goal: Merge
in Weekly GoalsApr 16, 2026
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 18, 2026

Copy link


Copy Markdown

🔔 1st Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 20, 2026

Copy link


Copy Markdown

🔔 2nd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@tnulltnull
added this to the 0.8 milestone
Apr 20, 2026
@Camillarhi
Camillarhi
commented
Apr 20, 2026

Copy link


Copy Markdown

Contributor
LGTM
@Camillarhi
Camillarhi
commented
Apr 21, 2026

Copy link


Copy Markdown

Contributor
This now needs a rebase, there's a merge conflict.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 22, 2026

Copy link


Copy Markdown

🔔 3rd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
joostjager
joostjager
reviewed
Apr 22, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure a generic client-side read throttle is the right abstraction here.
I think the motivation is mainly VSS-specific? For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Comment threadsrc/builder.rs
Comment threadsrc/io/utils.rs
Outdated

@tnull
tnull
commented
Apr 24, 2026

Copy link


Copy Markdown

CollaboratorAuthor
I am not sure a generic client-side read throttle is the right abstraction here.
Hmm, I tend to agree, though pre-existing.
I think the motivation is mainly VSS-specific?
Well, yes, presumably postgres could also benefit from it, though the store probably should switch to connection pooling anyways?
For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
@tnull
tnull
requested a review
from joostjagerApril 27, 2026 08:19
@tnulltnull
mentioned this pull request
Apr 27, 2026
 Open

joostjager
joostjager
reviewed
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
I think this is a good move, and later expand either towards protocol-level multi reads for vss, or perhaps generalize for other backends if the need arises.
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Discussed offline, decided we're not going with the BatchingStore abstraction right now, but only DRY up the read_ utility methods in io/utils.rs in this PR.
@tnulltnull
changed the title
DRY up batched KVStore reads with semaphore-based BatchingStoreDRY up batched KVStore reads utility methodsApr 28, 2026
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
5b8cebf to
22866abCompareApril 28, 2026 09:39
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 09:40
joostjager
joostjager
previously approved these changes
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, uncontentious. Rebase needed.
Comment threadsrc/io/utils.rs
@tnull
DRY up batched KVStore reads with read_all_objects helper
7aa48fa
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
22866ab to
7aa48faCompareApril 28, 2026 11:18
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Looks good, uncontentious. Rebase needed.
Rebased, sorry, forgot about that before.
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 11:19
@tnull
tnull
merged commit a8e2e5f
into
lightningdevkit:mainApr 29, 2026

16 of 21 checks passed

@github-project-automationgithub-project-automationBot
moved this from Goal: Merge
to Done
in Weekly GoalsApr 29, 2026
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@joostjagerjoostjagerjoostjager approved these changes

Assignees

@tnulltnull

Labels


None yet


Projects

Weekly Goals

Status: Done


Milestone

0.8

Development

Successfully merging this pull request may close these issues.

4 participants

@tnull@ldk-reviews-bot@Camillarhi@joostjager

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
DRY up batched `KVStore` reads utility methods by tnull · Pull Request #876 · lightningdevkit/ldk-node · GitHub
Skip to content
DRY up batched KVStore reads utility methods - #876
Merged
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Apr 29, 2026
Merged
DRY up batched KVStore reads utility methods#876
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Conversation
@tnull
@tnulltnull
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

Collaborator
DRY up batched KVStore reads with `read_all_objects` helper
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000

@tnull
tnull
requested a review
from joostjagerApril 15, 2026 13:54
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

👋 Thanks for assigning @joostjager as a reviewer!

I'll wait for their review and will help manage the review process.

Once they submit their review, I'll check if a second reviewer would be helpful.
@tnulltnull
self-assigned this
Apr 16, 2026
@tnulltnull
moved this to Goal: Merge
in Weekly GoalsApr 16, 2026
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 18, 2026

Copy link


Copy Markdown

🔔 1st Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 20, 2026

Copy link


Copy Markdown

🔔 2nd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@tnulltnull
added this to the 0.8 milestone
Apr 20, 2026
@Camillarhi
Camillarhi
commented
Apr 20, 2026

Copy link


Copy Markdown

Contributor
LGTM
@Camillarhi
Camillarhi
commented
Apr 21, 2026

Copy link


Copy Markdown

Contributor
This now needs a rebase, there's a merge conflict.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 22, 2026

Copy link


Copy Markdown

🔔 3rd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
joostjager
joostjager
reviewed
Apr 22, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure a generic client-side read throttle is the right abstraction here.
I think the motivation is mainly VSS-specific? For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Comment threadsrc/builder.rs
Comment threadsrc/io/utils.rs
Outdated

@tnull
tnull
commented
Apr 24, 2026

Copy link


Copy Markdown

CollaboratorAuthor
I am not sure a generic client-side read throttle is the right abstraction here.
Hmm, I tend to agree, though pre-existing.
I think the motivation is mainly VSS-specific?
Well, yes, presumably postgres could also benefit from it, though the store probably should switch to connection pooling anyways?
For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
@tnull
tnull
requested a review
from joostjagerApril 27, 2026 08:19
@tnulltnull
mentioned this pull request
Apr 27, 2026
 Open

joostjager
joostjager
reviewed
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
I think this is a good move, and later expand either towards protocol-level multi reads for vss, or perhaps generalize for other backends if the need arises.
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Discussed offline, decided we're not going with the BatchingStore abstraction right now, but only DRY up the read_ utility methods in io/utils.rs in this PR.
@tnulltnull
changed the title
DRY up batched KVStore reads with semaphore-based BatchingStoreDRY up batched KVStore reads utility methodsApr 28, 2026
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
5b8cebf to
22866abCompareApril 28, 2026 09:39
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 09:40
joostjager
joostjager
previously approved these changes
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, uncontentious. Rebase needed.
Comment threadsrc/io/utils.rs
@tnull
DRY up batched KVStore reads with read_all_objects helper
7aa48fa
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
22866ab to
7aa48faCompareApril 28, 2026 11:18
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Looks good, uncontentious. Rebase needed.
Rebased, sorry, forgot about that before.
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 11:19
@tnull
tnull
merged commit a8e2e5f
into
lightningdevkit:mainApr 29, 2026

16 of 21 checks passed

@github-project-automationgithub-project-automationBot
moved this from Goal: Merge
to Done
in Weekly GoalsApr 29, 2026
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@joostjagerjoostjagerjoostjager approved these changes

Assignees

@tnulltnull

Labels


None yet


Projects

Weekly Goals

Status: Done


Milestone

0.8

Development

Successfully merging this pull request may close these issues.

4 participants

@tnull@ldk-reviews-bot@Camillarhi@joostjager

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
DRY up batched `KVStore` reads utility methods by tnull · Pull Request #876 · lightningdevkit/ldk-node · GitHub
Skip to content
DRY up batched KVStore reads utility methods - #876
Merged
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Apr 29, 2026
Merged
DRY up batched KVStore reads utility methods#876
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Conversation
@tnull
@tnulltnull
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

Collaborator
DRY up batched KVStore reads with `read_all_objects` helper
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000

@tnull
tnull
requested a review
from joostjagerApril 15, 2026 13:54
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

👋 Thanks for assigning @joostjager as a reviewer!

I'll wait for their review and will help manage the review process.

Once they submit their review, I'll check if a second reviewer would be helpful.
@tnulltnull
self-assigned this
Apr 16, 2026
@tnulltnull
moved this to Goal: Merge
in Weekly GoalsApr 16, 2026
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 18, 2026

Copy link


Copy Markdown

🔔 1st Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 20, 2026

Copy link


Copy Markdown

🔔 2nd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@tnulltnull
added this to the 0.8 milestone
Apr 20, 2026
@Camillarhi
Camillarhi
commented
Apr 20, 2026

Copy link


Copy Markdown

Contributor
LGTM
@Camillarhi
Camillarhi
commented
Apr 21, 2026

Copy link


Copy Markdown

Contributor
This now needs a rebase, there's a merge conflict.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 22, 2026

Copy link


Copy Markdown

🔔 3rd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
joostjager
joostjager
reviewed
Apr 22, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure a generic client-side read throttle is the right abstraction here.
I think the motivation is mainly VSS-specific? For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Comment threadsrc/builder.rs
Comment threadsrc/io/utils.rs
Outdated

@tnull
tnull
commented
Apr 24, 2026

Copy link


Copy Markdown

CollaboratorAuthor
I am not sure a generic client-side read throttle is the right abstraction here.
Hmm, I tend to agree, though pre-existing.
I think the motivation is mainly VSS-specific?
Well, yes, presumably postgres could also benefit from it, though the store probably should switch to connection pooling anyways?
For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
@tnull
tnull
requested a review
from joostjagerApril 27, 2026 08:19
@tnulltnull
mentioned this pull request
Apr 27, 2026
 Open

joostjager
joostjager
reviewed
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
I think this is a good move, and later expand either towards protocol-level multi reads for vss, or perhaps generalize for other backends if the need arises.
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Discussed offline, decided we're not going with the BatchingStore abstraction right now, but only DRY up the read_ utility methods in io/utils.rs in this PR.
@tnulltnull
changed the title
DRY up batched KVStore reads with semaphore-based BatchingStoreDRY up batched KVStore reads utility methodsApr 28, 2026
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
5b8cebf to
22866abCompareApril 28, 2026 09:39
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 09:40
joostjager
joostjager
previously approved these changes
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, uncontentious. Rebase needed.
Comment threadsrc/io/utils.rs
@tnull
DRY up batched KVStore reads with read_all_objects helper
7aa48fa
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
22866ab to
7aa48faCompareApril 28, 2026 11:18
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Looks good, uncontentious. Rebase needed.
Rebased, sorry, forgot about that before.
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 11:19
@tnull
tnull
merged commit a8e2e5f
into
lightningdevkit:mainApr 29, 2026

16 of 21 checks passed

@github-project-automationgithub-project-automationBot
moved this from Goal: Merge
to Done
in Weekly GoalsApr 29, 2026
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@joostjagerjoostjagerjoostjager approved these changes

Assignees

@tnulltnull

Labels


None yet


Projects

Weekly Goals

Status: Done


Milestone

0.8

Development

Successfully merging this pull request may close these issues.

4 participants

@tnull@ldk-reviews-bot@Camillarhi@joostjager

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
DRY up batched `KVStore` reads utility methods by tnull · Pull Request #876 · lightningdevkit/ldk-node · GitHub
Skip to content
DRY up batched KVStore reads utility methods - #876
Merged
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Apr 29, 2026
Merged
DRY up batched KVStore reads utility methods#876
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Conversation
@tnull
@tnulltnull
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

Collaborator
DRY up batched KVStore reads with `read_all_objects` helper
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000

@tnull
tnull
requested a review
from joostjagerApril 15, 2026 13:54
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

👋 Thanks for assigning @joostjager as a reviewer!

I'll wait for their review and will help manage the review process.

Once they submit their review, I'll check if a second reviewer would be helpful.
@tnulltnull
self-assigned this
Apr 16, 2026
@tnulltnull
moved this to Goal: Merge
in Weekly GoalsApr 16, 2026
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 18, 2026

Copy link


Copy Markdown

🔔 1st Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 20, 2026

Copy link


Copy Markdown

🔔 2nd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@tnulltnull
added this to the 0.8 milestone
Apr 20, 2026
@Camillarhi
Camillarhi
commented
Apr 20, 2026

Copy link


Copy Markdown

Contributor
LGTM
@Camillarhi
Camillarhi
commented
Apr 21, 2026

Copy link


Copy Markdown

Contributor
This now needs a rebase, there's a merge conflict.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 22, 2026

Copy link


Copy Markdown

🔔 3rd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
joostjager
joostjager
reviewed
Apr 22, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure a generic client-side read throttle is the right abstraction here.
I think the motivation is mainly VSS-specific? For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Comment threadsrc/builder.rs
Comment threadsrc/io/utils.rs
Outdated

@tnull
tnull
commented
Apr 24, 2026

Copy link


Copy Markdown

CollaboratorAuthor
I am not sure a generic client-side read throttle is the right abstraction here.
Hmm, I tend to agree, though pre-existing.
I think the motivation is mainly VSS-specific?
Well, yes, presumably postgres could also benefit from it, though the store probably should switch to connection pooling anyways?
For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
@tnull
tnull
requested a review
from joostjagerApril 27, 2026 08:19
@tnulltnull
mentioned this pull request
Apr 27, 2026
 Open

joostjager
joostjager
reviewed
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
I think this is a good move, and later expand either towards protocol-level multi reads for vss, or perhaps generalize for other backends if the need arises.
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Discussed offline, decided we're not going with the BatchingStore abstraction right now, but only DRY up the read_ utility methods in io/utils.rs in this PR.
@tnulltnull
changed the title
DRY up batched KVStore reads with semaphore-based BatchingStoreDRY up batched KVStore reads utility methodsApr 28, 2026
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
5b8cebf to
22866abCompareApril 28, 2026 09:39
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 09:40
joostjager
joostjager
previously approved these changes
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, uncontentious. Rebase needed.
Comment threadsrc/io/utils.rs
@tnull
DRY up batched KVStore reads with read_all_objects helper
7aa48fa
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
22866ab to
7aa48faCompareApril 28, 2026 11:18
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Looks good, uncontentious. Rebase needed.
Rebased, sorry, forgot about that before.
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 11:19
@tnull
tnull
merged commit a8e2e5f
into
lightningdevkit:mainApr 29, 2026

16 of 21 checks passed

@github-project-automationgithub-project-automationBot
moved this from Goal: Merge
to Done
in Weekly GoalsApr 29, 2026
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@joostjagerjoostjagerjoostjager approved these changes

Assignees

@tnulltnull

Labels


None yet


Projects

Weekly Goals

Status: Done


Milestone

0.8

Development

Successfully merging this pull request may close these issues.

4 participants

@tnull@ldk-reviews-bot@Camillarhi@joostjager

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
DRY up batched `KVStore` reads utility methods by tnull · Pull Request #876 · lightningdevkit/ldk-node · GitHub
Skip to content
DRY up batched KVStore reads utility methods - #876
Merged
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Apr 29, 2026
Merged
DRY up batched KVStore reads utility methods#876
tnull merged 1 commit into
lightningdevkit:mainfrom 
tnull:2026-04-batching-store
Conversation
@tnull
@tnulltnull
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

Collaborator
DRY up batched KVStore reads with `read_all_objects` helper
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000

@tnull
tnull
requested a review
from joostjagerApril 15, 2026 13:54
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 15, 2026•

edited

Loading

Copy link


Copy Markdown

👋 Thanks for assigning @joostjager as a reviewer!

I'll wait for their review and will help manage the review process.

Once they submit their review, I'll check if a second reviewer would be helpful.
@tnulltnull
self-assigned this
Apr 16, 2026
@tnulltnull
moved this to Goal: Merge
in Weekly GoalsApr 16, 2026
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 18, 2026

Copy link


Copy Markdown

🔔 1st Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 20, 2026

Copy link


Copy Markdown

🔔 2nd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
@tnulltnull
added this to the 0.8 milestone
Apr 20, 2026
@Camillarhi
Camillarhi
commented
Apr 20, 2026

Copy link


Copy Markdown

Contributor
LGTM
@Camillarhi
Camillarhi
commented
Apr 21, 2026

Copy link


Copy Markdown

Contributor
This now needs a rebase, there's a merge conflict.
@ldk-reviews-bot
ldk-reviews-bot
commented
Apr 22, 2026

Copy link


Copy Markdown

🔔 3rd Reminder
Hey @joostjager! This PR has been waiting for your review.

Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.
joostjager
joostjager
reviewed
Apr 22, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure a generic client-side read throttle is the right abstraction here.
I think the motivation is mainly VSS-specific? For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Comment threadsrc/builder.rs
Comment threadsrc/io/utils.rs
Outdated

@tnull
tnull
commented
Apr 24, 2026

Copy link


Copy Markdown

CollaboratorAuthor
I am not sure a generic client-side read throttle is the right abstraction here.
Hmm, I tend to agree, though pre-existing.
I think the motivation is mainly VSS-specific?
Well, yes, presumably postgres could also benefit from it, though the store probably should switch to connection pooling anyways?
For local stores such as SQLite, this mostly limits task fan-out rather than real backend concurrency. Perhaps it should be implemented only in the VSS client. And perhaps longer term, a multi-key read would be helpful in the VSS protocol?
Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
@tnull
tnull
requested a review
from joostjagerApril 27, 2026 08:19
@tnulltnull
mentioned this pull request
Apr 27, 2026
 Open

joostjager
joostjager
reviewed
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, maybe for now I should just switch to wrap VssStore in BatchingStore in this PR? WDYT?
I think this is a good move, and later expand either towards protocol-level multi reads for vss, or perhaps generalize for other backends if the need arises.
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Discussed offline, decided we're not going with the BatchingStore abstraction right now, but only DRY up the read_ utility methods in io/utils.rs in this PR.
@tnulltnull
changed the title
DRY up batched KVStore reads with semaphore-based BatchingStoreDRY up batched KVStore reads utility methodsApr 28, 2026
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
5b8cebf to
22866abCompareApril 28, 2026 09:39
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 09:40
joostjager
joostjager
previously approved these changes
Apr 28, 2026
View reviewed changes
@joostjagerjoostjager
left a comment


Copy link


Copy Markdown

Contributor
Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, uncontentious. Rebase needed.
Comment threadsrc/io/utils.rs
@tnull
DRY up batched KVStore reads with read_all_objects helper
7aa48fa
The parallel `JoinSet`-based batching loop was duplicated across
`read_payments` and `read_pending_payments`. Extract it into a generic
`read_all_objects<T: Readable>` helper that callers invoke directly
with the relevant namespace constants. Per-type log messages are
preserved via `std::any::type_name::<T>()`.
Co-Authored-By: HAL 9000
@tnull
tnullforce-pushed
the
2026-04-batching-store
branch
from
22866ab to
7aa48faCompareApril 28, 2026 11:18
@tnull
tnull
commented
Apr 28, 2026

Copy link


Copy Markdown

CollaboratorAuthor
Looks good, uncontentious. Rebase needed.
Rebased, sorry, forgot about that before.
@tnull
tnull
requested a review
from joostjagerApril 28, 2026 11:19
@tnull
tnull
merged commit a8e2e5f
into
lightningdevkit:mainApr 29, 2026

16 of 21 checks passed

@github-project-automationgithub-project-automationBot
moved this from Goal: Merge
to Done
in Weekly GoalsApr 29, 2026
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@joostjagerjoostjagerjoostjager approved these changes

Assignees

@tnulltnull

Labels


None yet


Projects

Weekly Goals

Status: Done


Milestone

0.8

Development

Successfully merging this pull request may close these issues.

4 participants

@tnull@ldk-reviews-bot@Camillarhi@joostjager