Skip to content

Channelmanager: improve block connection logging - #4586

Open
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging
Open

Channelmanager: improve block connection logging#4586
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging

Conversation

@Alkamal01

Copy link
Copy Markdown
Contributor

Channelmanager: improve block connection logging

Fixes#2348. Supersedes #4420.

best_block_updated was logging at TRACE, making it impossible to track chain tip progress without enabling full trace logging. This upgrades it to INFO.

Also adds per-txid DEBUG logs in transactions_confirmed so individual transactions triggering channel updates are visible at a useful log level.

The original PR #4420 also added an INFO log in filtered_block_connected, but that duplicates the one in best_block_updated (which filtered_block_connected calls directly). That log is left out here.

Upgrade best_block_updated log from TRACE to INFO so chain tip
updates are visible without enabling full trace logging.
Add per-txid DEBUG logs in transactions_confirmed to make it easier
to identify which transactions triggered channel updates.
@ldk-reviews-bot

ldk-reviews-bot commented May 2, 2026

Copy link
Copy Markdown

I've assigned @valentinewallace 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.

Comment on lines +15971 to +15973
for (_, tx) in txdata.iter() {
log_debug!(self.logger, "Confirmed transaction {} in block {} at height {}", tx.compute_txid(), block_hash, height);
}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

compute_txid() performs a double-SHA256 over the serialized transaction, and the log_given_level! macro evaluates its arguments unconditionally (the level check is inside the Logger::log implementation, not before argument evaluation). This means the loop runs and hashes every transaction even when the logger's level is above DEBUG.

Consider either:

  1. Guarding the loop behind a level check, or
  2. Folding these per-txid details into the existing TRACE log, or
  3. Using a lazy wrapper (e.g., a Display impl that computes on fmt) — though this still wouldn't avoid the loop itself.

While txdata only contains matching transactions (not the full block), computing txids unconditionally on every block connection is unnecessary overhead for users who don't have DEBUG enabled.

@ldk-claude-review-bot

ldk-claude-review-bot commented May 2, 2026

Copy link
Copy Markdown
Collaborator

Both prior issues are resolved in the latest commit:

  1. Transaction type path (prior comment on line 15971): Fixed — now uses Transaction directly (in scope from line 24) instead of the private chain::transaction::Transaction path.

  2. Unconditional compute_txid() (prior comment on line 15979): Fixed — the LazyTxid wrapper defers compute_txid() to the Display::fmt implementation. Since format_args! captures a reference to LazyTxid without invoking Display::fmt, and the Logger::log method only formats the message when the level check passes, the double-SHA256 is only computed when DEBUG logging is actually enabled.

No new issues found. The code is clean.

No issues found.

Both previously flagged issues have been addressed in the latest commit (985a82bb):

  • The Transaction type reference now uses the in-scope import instead of a private module path.
  • compute_txid() is correctly deferred via the LazyTxidDisplay wrapper, avoiding unnecessary hashing when DEBUG is disabled.

@codecov

codecovBot commented May 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.16%. Comparing base (6573d42) to head (985a82b).
⚠️ Report is 215 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #4586 +/- ##
==========================================
+ Coverage 86.99% 87.16% +0.17% 
==========================================
Files 163 161 -2 Lines 109008 109266 +258 Branches 109008 109266 +258 ==========================================
+ Hits 94828 95247 +419 + Misses 11696 11544 -152 + Partials 2484 2475 -9 
FlagCoverage Δ
fuzzing?
fuzzing-fake-hashes31.21% <100.00%> (?)
fuzzing-real-hashes22.94% <100.00%> (?)
tests86.23% <100.00%> (+0.13%)⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadlightning/src/ln/channelmanager.rs Outdated

let block_hash = header.block_hash();
log_trace!(self.logger, "{} transactions included in block {} at height {} provided", txdata.len(), block_hash, height);
struct LazyTxid<'a>(&'a chain::transaction::Transaction);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

chain::transaction::Transaction references a private import — chain/transaction.rs has use bitcoin::transaction::Transaction; (no pub), so this name is not accessible from outside that module. This should fail to compile with error[E0603]: import 'Transaction' is private.

Transaction is already imported at line 24 of this file via use bitcoin::transaction::Transaction;, so the fix is simply:

Suggested change
structLazyTxid<'a>(&'achain::transaction::Transaction);
structLazyTxid<'a>(&'aTransaction);

…gging
Use a lazy Display wrapper to format confirmed txids, preventing unconditional hashing when DEBUG logging is disabled.
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! 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.

@valentinewallace

Copy link
Copy Markdown
Contributor

Superseded by #4659

@TheBlueMatt

Copy link
Copy Markdown
Collaborator

reopening per #4659 (comment)

@TheBlueMattTheBlueMatt reopened this Jun 9, 2026
@kamal-ogtl

Copy link
Copy Markdown

reopening per #4659 (comment)

Thanks for reopening!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve block connection logging

6 participants

@Alkamal01@ldk-reviews-bot@ldk-claude-review-bot@valentinewallace@TheBlueMatt@kamal-ogtl
, '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" + '
Channelmanager: improve block connection logging by Alkamal01 · Pull Request #4586 · lightningdevkit/rust-lightning · GitHub
Skip to content

Channelmanager: improve block connection logging - #4586

Open
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging
Open

Channelmanager: improve block connection logging#4586
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging

Conversation

@Alkamal01

Copy link
Copy Markdown
Contributor

Channelmanager: improve block connection logging

Fixes#2348. Supersedes #4420.

best_block_updated was logging at TRACE, making it impossible to track chain tip progress without enabling full trace logging. This upgrades it to INFO.

Also adds per-txid DEBUG logs in transactions_confirmed so individual transactions triggering channel updates are visible at a useful log level.

The original PR #4420 also added an INFO log in filtered_block_connected, but that duplicates the one in best_block_updated (which filtered_block_connected calls directly). That log is left out here.

Upgrade best_block_updated log from TRACE to INFO so chain tip
updates are visible without enabling full trace logging.
Add per-txid DEBUG logs in transactions_confirmed to make it easier
to identify which transactions triggered channel updates.
@ldk-reviews-bot

ldk-reviews-bot commented May 2, 2026

Copy link
Copy Markdown

I've assigned @valentinewallace 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.

Comment on lines +15971 to +15973
for (_, tx) in txdata.iter() {
log_debug!(self.logger, "Confirmed transaction {} in block {} at height {}", tx.compute_txid(), block_hash, height);
}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

compute_txid() performs a double-SHA256 over the serialized transaction, and the log_given_level! macro evaluates its arguments unconditionally (the level check is inside the Logger::log implementation, not before argument evaluation). This means the loop runs and hashes every transaction even when the logger's level is above DEBUG.

Consider either:

  1. Guarding the loop behind a level check, or
  2. Folding these per-txid details into the existing TRACE log, or
  3. Using a lazy wrapper (e.g., a Display impl that computes on fmt) — though this still wouldn't avoid the loop itself.

While txdata only contains matching transactions (not the full block), computing txids unconditionally on every block connection is unnecessary overhead for users who don't have DEBUG enabled.

@ldk-claude-review-bot

ldk-claude-review-bot commented May 2, 2026

Copy link
Copy Markdown
Collaborator

Both prior issues are resolved in the latest commit:

  1. Transaction type path (prior comment on line 15971): Fixed — now uses Transaction directly (in scope from line 24) instead of the private chain::transaction::Transaction path.

  2. Unconditional compute_txid() (prior comment on line 15979): Fixed — the LazyTxid wrapper defers compute_txid() to the Display::fmt implementation. Since format_args! captures a reference to LazyTxid without invoking Display::fmt, and the Logger::log method only formats the message when the level check passes, the double-SHA256 is only computed when DEBUG logging is actually enabled.

No new issues found. The code is clean.

No issues found.

Both previously flagged issues have been addressed in the latest commit (985a82bb):

  • The Transaction type reference now uses the in-scope import instead of a private module path.
  • compute_txid() is correctly deferred via the LazyTxidDisplay wrapper, avoiding unnecessary hashing when DEBUG is disabled.

@codecov

codecovBot commented May 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.16%. Comparing base (6573d42) to head (985a82b).
⚠️ Report is 215 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #4586 +/- ##
==========================================
+ Coverage 86.99% 87.16% +0.17% 
==========================================
Files 163 161 -2 Lines 109008 109266 +258 Branches 109008 109266 +258 ==========================================
+ Hits 94828 95247 +419 + Misses 11696 11544 -152 + Partials 2484 2475 -9 
FlagCoverage Δ
fuzzing?
fuzzing-fake-hashes31.21% <100.00%> (?)
fuzzing-real-hashes22.94% <100.00%> (?)
tests86.23% <100.00%> (+0.13%)⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadlightning/src/ln/channelmanager.rs Outdated

let block_hash = header.block_hash();
log_trace!(self.logger, "{} transactions included in block {} at height {} provided", txdata.len(), block_hash, height);
struct LazyTxid<'a>(&'a chain::transaction::Transaction);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

chain::transaction::Transaction references a private import — chain/transaction.rs has use bitcoin::transaction::Transaction; (no pub), so this name is not accessible from outside that module. This should fail to compile with error[E0603]: import 'Transaction' is private.

Transaction is already imported at line 24 of this file via use bitcoin::transaction::Transaction;, so the fix is simply:

Suggested change
structLazyTxid<'a>(&'achain::transaction::Transaction);
structLazyTxid<'a>(&'aTransaction);

…gging
Use a lazy Display wrapper to format confirmed txids, preventing unconditional hashing when DEBUG logging is disabled.
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! 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.

@valentinewallace

Copy link
Copy Markdown
Contributor

Superseded by #4659

@TheBlueMatt

Copy link
Copy Markdown
Collaborator

reopening per #4659 (comment)

@TheBlueMattTheBlueMatt reopened this Jun 9, 2026
@kamal-ogtl

Copy link
Copy Markdown

reopening per #4659 (comment)

Thanks for reopening!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve block connection logging

6 participants

@Alkamal01@ldk-reviews-bot@ldk-claude-review-bot@valentinewallace@TheBlueMatt@kamal-ogtl
, '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('^' + ".*" + ' Channelmanager: improve block connection logging by Alkamal01 · Pull Request #4586 · lightningdevkit/rust-lightning · GitHub
Skip to content

Channelmanager: improve block connection logging - #4586

Open
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging
Open

Channelmanager: improve block connection logging#4586
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging

Conversation

@Alkamal01

Copy link
Copy Markdown
Contributor

Channelmanager: improve block connection logging

Fixes#2348. Supersedes #4420.

best_block_updated was logging at TRACE, making it impossible to track chain tip progress without enabling full trace logging. This upgrades it to INFO.

Also adds per-txid DEBUG logs in transactions_confirmed so individual transactions triggering channel updates are visible at a useful log level.

The original PR #4420 also added an INFO log in filtered_block_connected, but that duplicates the one in best_block_updated (which filtered_block_connected calls directly). That log is left out here.

Upgrade best_block_updated log from TRACE to INFO so chain tip
updates are visible without enabling full trace logging.
Add per-txid DEBUG logs in transactions_confirmed to make it easier
to identify which transactions triggered channel updates.
@ldk-reviews-bot

ldk-reviews-bot commented May 2, 2026

Copy link
Copy Markdown

I've assigned @valentinewallace 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.

Comment on lines +15971 to +15973
for (_, tx) in txdata.iter() {
log_debug!(self.logger, "Confirmed transaction {} in block {} at height {}", tx.compute_txid(), block_hash, height);
}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

compute_txid() performs a double-SHA256 over the serialized transaction, and the log_given_level! macro evaluates its arguments unconditionally (the level check is inside the Logger::log implementation, not before argument evaluation). This means the loop runs and hashes every transaction even when the logger's level is above DEBUG.

Consider either:

  1. Guarding the loop behind a level check, or
  2. Folding these per-txid details into the existing TRACE log, or
  3. Using a lazy wrapper (e.g., a Display impl that computes on fmt) — though this still wouldn't avoid the loop itself.

While txdata only contains matching transactions (not the full block), computing txids unconditionally on every block connection is unnecessary overhead for users who don't have DEBUG enabled.

@ldk-claude-review-bot

ldk-claude-review-bot commented May 2, 2026

Copy link
Copy Markdown
Collaborator

Both prior issues are resolved in the latest commit:

  1. Transaction type path (prior comment on line 15971): Fixed — now uses Transaction directly (in scope from line 24) instead of the private chain::transaction::Transaction path.

  2. Unconditional compute_txid() (prior comment on line 15979): Fixed — the LazyTxid wrapper defers compute_txid() to the Display::fmt implementation. Since format_args! captures a reference to LazyTxid without invoking Display::fmt, and the Logger::log method only formats the message when the level check passes, the double-SHA256 is only computed when DEBUG logging is actually enabled.

No new issues found. The code is clean.

No issues found.

Both previously flagged issues have been addressed in the latest commit (985a82bb):

  • The Transaction type reference now uses the in-scope import instead of a private module path.
  • compute_txid() is correctly deferred via the LazyTxidDisplay wrapper, avoiding unnecessary hashing when DEBUG is disabled.

@codecov

codecovBot commented May 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.16%. Comparing base (6573d42) to head (985a82b).
⚠️ Report is 215 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #4586 +/- ##
==========================================
+ Coverage 86.99% 87.16% +0.17% 
==========================================
Files 163 161 -2 Lines 109008 109266 +258 Branches 109008 109266 +258 ==========================================
+ Hits 94828 95247 +419 + Misses 11696 11544 -152 + Partials 2484 2475 -9 
FlagCoverage Δ
fuzzing?
fuzzing-fake-hashes31.21% <100.00%> (?)
fuzzing-real-hashes22.94% <100.00%> (?)
tests86.23% <100.00%> (+0.13%)⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadlightning/src/ln/channelmanager.rs Outdated

let block_hash = header.block_hash();
log_trace!(self.logger, "{} transactions included in block {} at height {} provided", txdata.len(), block_hash, height);
struct LazyTxid<'a>(&'a chain::transaction::Transaction);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

chain::transaction::Transaction references a private import — chain/transaction.rs has use bitcoin::transaction::Transaction; (no pub), so this name is not accessible from outside that module. This should fail to compile with error[E0603]: import 'Transaction' is private.

Transaction is already imported at line 24 of this file via use bitcoin::transaction::Transaction;, so the fix is simply:

Suggested change
structLazyTxid<'a>(&'achain::transaction::Transaction);
structLazyTxid<'a>(&'aTransaction);

…gging
Use a lazy Display wrapper to format confirmed txids, preventing unconditional hashing when DEBUG logging is disabled.
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! 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.

@valentinewallace

Copy link
Copy Markdown
Contributor

Superseded by #4659

@TheBlueMatt

Copy link
Copy Markdown
Collaborator

reopening per #4659 (comment)

@TheBlueMattTheBlueMatt reopened this Jun 9, 2026
@kamal-ogtl

Copy link
Copy Markdown

reopening per #4659 (comment)

Thanks for reopening!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve block connection logging

6 participants

@Alkamal01@ldk-reviews-bot@ldk-claude-review-bot@valentinewallace@TheBlueMatt@kamal-ogtl
, '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('^' + ".*" + ' Channelmanager: improve block connection logging by Alkamal01 · Pull Request #4586 · lightningdevkit/rust-lightning · GitHub
Skip to content

Channelmanager: improve block connection logging - #4586

Open
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging
Open

Channelmanager: improve block connection logging#4586
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging

Conversation

@Alkamal01

Copy link
Copy Markdown
Contributor

Channelmanager: improve block connection logging

Fixes#2348. Supersedes #4420.

best_block_updated was logging at TRACE, making it impossible to track chain tip progress without enabling full trace logging. This upgrades it to INFO.

Also adds per-txid DEBUG logs in transactions_confirmed so individual transactions triggering channel updates are visible at a useful log level.

The original PR #4420 also added an INFO log in filtered_block_connected, but that duplicates the one in best_block_updated (which filtered_block_connected calls directly). That log is left out here.

Upgrade best_block_updated log from TRACE to INFO so chain tip
updates are visible without enabling full trace logging.
Add per-txid DEBUG logs in transactions_confirmed to make it easier
to identify which transactions triggered channel updates.
@ldk-reviews-bot

ldk-reviews-bot commented May 2, 2026

Copy link
Copy Markdown

I've assigned @valentinewallace 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.

Comment on lines +15971 to +15973
for (_, tx) in txdata.iter() {
log_debug!(self.logger, "Confirmed transaction {} in block {} at height {}", tx.compute_txid(), block_hash, height);
}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

compute_txid() performs a double-SHA256 over the serialized transaction, and the log_given_level! macro evaluates its arguments unconditionally (the level check is inside the Logger::log implementation, not before argument evaluation). This means the loop runs and hashes every transaction even when the logger's level is above DEBUG.

Consider either:

  1. Guarding the loop behind a level check, or
  2. Folding these per-txid details into the existing TRACE log, or
  3. Using a lazy wrapper (e.g., a Display impl that computes on fmt) — though this still wouldn't avoid the loop itself.

While txdata only contains matching transactions (not the full block), computing txids unconditionally on every block connection is unnecessary overhead for users who don't have DEBUG enabled.

@ldk-claude-review-bot

ldk-claude-review-bot commented May 2, 2026

Copy link
Copy Markdown
Collaborator

Both prior issues are resolved in the latest commit:

  1. Transaction type path (prior comment on line 15971): Fixed — now uses Transaction directly (in scope from line 24) instead of the private chain::transaction::Transaction path.

  2. Unconditional compute_txid() (prior comment on line 15979): Fixed — the LazyTxid wrapper defers compute_txid() to the Display::fmt implementation. Since format_args! captures a reference to LazyTxid without invoking Display::fmt, and the Logger::log method only formats the message when the level check passes, the double-SHA256 is only computed when DEBUG logging is actually enabled.

No new issues found. The code is clean.

No issues found.

Both previously flagged issues have been addressed in the latest commit (985a82bb):

  • The Transaction type reference now uses the in-scope import instead of a private module path.
  • compute_txid() is correctly deferred via the LazyTxidDisplay wrapper, avoiding unnecessary hashing when DEBUG is disabled.

@codecov

codecovBot commented May 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.16%. Comparing base (6573d42) to head (985a82b).
⚠️ Report is 215 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #4586 +/- ##
==========================================
+ Coverage 86.99% 87.16% +0.17% 
==========================================
Files 163 161 -2 Lines 109008 109266 +258 Branches 109008 109266 +258 ==========================================
+ Hits 94828 95247 +419 + Misses 11696 11544 -152 + Partials 2484 2475 -9 
FlagCoverage Δ
fuzzing?
fuzzing-fake-hashes31.21% <100.00%> (?)
fuzzing-real-hashes22.94% <100.00%> (?)
tests86.23% <100.00%> (+0.13%)⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadlightning/src/ln/channelmanager.rs Outdated

let block_hash = header.block_hash();
log_trace!(self.logger, "{} transactions included in block {} at height {} provided", txdata.len(), block_hash, height);
struct LazyTxid<'a>(&'a chain::transaction::Transaction);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

chain::transaction::Transaction references a private import — chain/transaction.rs has use bitcoin::transaction::Transaction; (no pub), so this name is not accessible from outside that module. This should fail to compile with error[E0603]: import 'Transaction' is private.

Transaction is already imported at line 24 of this file via use bitcoin::transaction::Transaction;, so the fix is simply:

Suggested change
structLazyTxid<'a>(&'achain::transaction::Transaction);
structLazyTxid<'a>(&'aTransaction);

…gging
Use a lazy Display wrapper to format confirmed txids, preventing unconditional hashing when DEBUG logging is disabled.
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! 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.

@valentinewallace

Copy link
Copy Markdown
Contributor

Superseded by #4659

@TheBlueMatt

Copy link
Copy Markdown
Collaborator

reopening per #4659 (comment)

@TheBlueMattTheBlueMatt reopened this Jun 9, 2026
@kamal-ogtl

Copy link
Copy Markdown

reopening per #4659 (comment)

Thanks for reopening!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve block connection logging

6 participants

@Alkamal01@ldk-reviews-bot@ldk-claude-review-bot@valentinewallace@TheBlueMatt@kamal-ogtl
, '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" + ' Channelmanager: improve block connection logging by Alkamal01 · Pull Request #4586 · lightningdevkit/rust-lightning · GitHub
Skip to content

Channelmanager: improve block connection logging - #4586

Open
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging
Open

Channelmanager: improve block connection logging#4586
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging

Conversation

@Alkamal01

Copy link
Copy Markdown
Contributor

Channelmanager: improve block connection logging

Fixes#2348. Supersedes #4420.

best_block_updated was logging at TRACE, making it impossible to track chain tip progress without enabling full trace logging. This upgrades it to INFO.

Also adds per-txid DEBUG logs in transactions_confirmed so individual transactions triggering channel updates are visible at a useful log level.

The original PR #4420 also added an INFO log in filtered_block_connected, but that duplicates the one in best_block_updated (which filtered_block_connected calls directly). That log is left out here.

Upgrade best_block_updated log from TRACE to INFO so chain tip
updates are visible without enabling full trace logging.
Add per-txid DEBUG logs in transactions_confirmed to make it easier
to identify which transactions triggered channel updates.
@ldk-reviews-bot

ldk-reviews-bot commented May 2, 2026

Copy link
Copy Markdown

I've assigned @valentinewallace 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.

Comment on lines +15971 to +15973
for (_, tx) in txdata.iter() {
log_debug!(self.logger, "Confirmed transaction {} in block {} at height {}", tx.compute_txid(), block_hash, height);
}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

compute_txid() performs a double-SHA256 over the serialized transaction, and the log_given_level! macro evaluates its arguments unconditionally (the level check is inside the Logger::log implementation, not before argument evaluation). This means the loop runs and hashes every transaction even when the logger's level is above DEBUG.

Consider either:

  1. Guarding the loop behind a level check, or
  2. Folding these per-txid details into the existing TRACE log, or
  3. Using a lazy wrapper (e.g., a Display impl that computes on fmt) — though this still wouldn't avoid the loop itself.

While txdata only contains matching transactions (not the full block), computing txids unconditionally on every block connection is unnecessary overhead for users who don't have DEBUG enabled.

@ldk-claude-review-bot

ldk-claude-review-bot commented May 2, 2026

Copy link
Copy Markdown
Collaborator

Both prior issues are resolved in the latest commit:

  1. Transaction type path (prior comment on line 15971): Fixed — now uses Transaction directly (in scope from line 24) instead of the private chain::transaction::Transaction path.

  2. Unconditional compute_txid() (prior comment on line 15979): Fixed — the LazyTxid wrapper defers compute_txid() to the Display::fmt implementation. Since format_args! captures a reference to LazyTxid without invoking Display::fmt, and the Logger::log method only formats the message when the level check passes, the double-SHA256 is only computed when DEBUG logging is actually enabled.

No new issues found. The code is clean.

No issues found.

Both previously flagged issues have been addressed in the latest commit (985a82bb):

  • The Transaction type reference now uses the in-scope import instead of a private module path.
  • compute_txid() is correctly deferred via the LazyTxidDisplay wrapper, avoiding unnecessary hashing when DEBUG is disabled.

@codecov

codecovBot commented May 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.16%. Comparing base (6573d42) to head (985a82b).
⚠️ Report is 215 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #4586 +/- ##
==========================================
+ Coverage 86.99% 87.16% +0.17% 
==========================================
Files 163 161 -2 Lines 109008 109266 +258 Branches 109008 109266 +258 ==========================================
+ Hits 94828 95247 +419 + Misses 11696 11544 -152 + Partials 2484 2475 -9 
FlagCoverage Δ
fuzzing?
fuzzing-fake-hashes31.21% <100.00%> (?)
fuzzing-real-hashes22.94% <100.00%> (?)
tests86.23% <100.00%> (+0.13%)⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadlightning/src/ln/channelmanager.rs Outdated

let block_hash = header.block_hash();
log_trace!(self.logger, "{} transactions included in block {} at height {} provided", txdata.len(), block_hash, height);
struct LazyTxid<'a>(&'a chain::transaction::Transaction);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

chain::transaction::Transaction references a private import — chain/transaction.rs has use bitcoin::transaction::Transaction; (no pub), so this name is not accessible from outside that module. This should fail to compile with error[E0603]: import 'Transaction' is private.

Transaction is already imported at line 24 of this file via use bitcoin::transaction::Transaction;, so the fix is simply:

Suggested change
structLazyTxid<'a>(&'achain::transaction::Transaction);
structLazyTxid<'a>(&'aTransaction);

…gging
Use a lazy Display wrapper to format confirmed txids, preventing unconditional hashing when DEBUG logging is disabled.
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! 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.

@valentinewallace

Copy link
Copy Markdown
Contributor

Superseded by #4659

@TheBlueMatt

Copy link
Copy Markdown
Collaborator

reopening per #4659 (comment)

@TheBlueMattTheBlueMatt reopened this Jun 9, 2026
@kamal-ogtl

Copy link
Copy Markdown

reopening per #4659 (comment)

Thanks for reopening!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve block connection logging

6 participants

@Alkamal01@ldk-reviews-bot@ldk-claude-review-bot@valentinewallace@TheBlueMatt@kamal-ogtl
, '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('^' + ".*" + ' Channelmanager: improve block connection logging by Alkamal01 · Pull Request #4586 · lightningdevkit/rust-lightning · GitHub
Skip to content

Channelmanager: improve block connection logging - #4586

Open
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging
Open

Channelmanager: improve block connection logging#4586
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging

Conversation

@Alkamal01

Copy link
Copy Markdown
Contributor

Channelmanager: improve block connection logging

Fixes#2348. Supersedes #4420.

best_block_updated was logging at TRACE, making it impossible to track chain tip progress without enabling full trace logging. This upgrades it to INFO.

Also adds per-txid DEBUG logs in transactions_confirmed so individual transactions triggering channel updates are visible at a useful log level.

The original PR #4420 also added an INFO log in filtered_block_connected, but that duplicates the one in best_block_updated (which filtered_block_connected calls directly). That log is left out here.

Upgrade best_block_updated log from TRACE to INFO so chain tip
updates are visible without enabling full trace logging.
Add per-txid DEBUG logs in transactions_confirmed to make it easier
to identify which transactions triggered channel updates.
@ldk-reviews-bot

ldk-reviews-bot commented May 2, 2026

Copy link
Copy Markdown

I've assigned @valentinewallace 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.

Comment on lines +15971 to +15973
for (_, tx) in txdata.iter() {
log_debug!(self.logger, "Confirmed transaction {} in block {} at height {}", tx.compute_txid(), block_hash, height);
}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

compute_txid() performs a double-SHA256 over the serialized transaction, and the log_given_level! macro evaluates its arguments unconditionally (the level check is inside the Logger::log implementation, not before argument evaluation). This means the loop runs and hashes every transaction even when the logger's level is above DEBUG.

Consider either:

  1. Guarding the loop behind a level check, or
  2. Folding these per-txid details into the existing TRACE log, or
  3. Using a lazy wrapper (e.g., a Display impl that computes on fmt) — though this still wouldn't avoid the loop itself.

While txdata only contains matching transactions (not the full block), computing txids unconditionally on every block connection is unnecessary overhead for users who don't have DEBUG enabled.

@ldk-claude-review-bot

ldk-claude-review-bot commented May 2, 2026

Copy link
Copy Markdown
Collaborator

Both prior issues are resolved in the latest commit:

  1. Transaction type path (prior comment on line 15971): Fixed — now uses Transaction directly (in scope from line 24) instead of the private chain::transaction::Transaction path.

  2. Unconditional compute_txid() (prior comment on line 15979): Fixed — the LazyTxid wrapper defers compute_txid() to the Display::fmt implementation. Since format_args! captures a reference to LazyTxid without invoking Display::fmt, and the Logger::log method only formats the message when the level check passes, the double-SHA256 is only computed when DEBUG logging is actually enabled.

No new issues found. The code is clean.

No issues found.

Both previously flagged issues have been addressed in the latest commit (985a82bb):

  • The Transaction type reference now uses the in-scope import instead of a private module path.
  • compute_txid() is correctly deferred via the LazyTxidDisplay wrapper, avoiding unnecessary hashing when DEBUG is disabled.

@codecov

codecovBot commented May 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.16%. Comparing base (6573d42) to head (985a82b).
⚠️ Report is 215 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #4586 +/- ##
==========================================
+ Coverage 86.99% 87.16% +0.17% 
==========================================
Files 163 161 -2 Lines 109008 109266 +258 Branches 109008 109266 +258 ==========================================
+ Hits 94828 95247 +419 + Misses 11696 11544 -152 + Partials 2484 2475 -9 
FlagCoverage Δ
fuzzing?
fuzzing-fake-hashes31.21% <100.00%> (?)
fuzzing-real-hashes22.94% <100.00%> (?)
tests86.23% <100.00%> (+0.13%)⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadlightning/src/ln/channelmanager.rs Outdated

let block_hash = header.block_hash();
log_trace!(self.logger, "{} transactions included in block {} at height {} provided", txdata.len(), block_hash, height);
struct LazyTxid<'a>(&'a chain::transaction::Transaction);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

chain::transaction::Transaction references a private import — chain/transaction.rs has use bitcoin::transaction::Transaction; (no pub), so this name is not accessible from outside that module. This should fail to compile with error[E0603]: import 'Transaction' is private.

Transaction is already imported at line 24 of this file via use bitcoin::transaction::Transaction;, so the fix is simply:

Suggested change
structLazyTxid<'a>(&'achain::transaction::Transaction);
structLazyTxid<'a>(&'aTransaction);

…gging
Use a lazy Display wrapper to format confirmed txids, preventing unconditional hashing when DEBUG logging is disabled.
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! 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.

@valentinewallace

Copy link
Copy Markdown
Contributor

Superseded by #4659

@TheBlueMatt

Copy link
Copy Markdown
Collaborator

reopening per #4659 (comment)

@TheBlueMattTheBlueMatt reopened this Jun 9, 2026
@kamal-ogtl

Copy link
Copy Markdown

reopening per #4659 (comment)

Thanks for reopening!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve block connection logging

6 participants

@Alkamal01@ldk-reviews-bot@ldk-claude-review-bot@valentinewallace@TheBlueMatt@kamal-ogtl
, '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); } })(); })(); Channelmanager: improve block connection logging by Alkamal01 · Pull Request #4586 · lightningdevkit/rust-lightning · GitHub
Skip to content

Channelmanager: improve block connection logging - #4586

Open
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging
Open

Channelmanager: improve block connection logging#4586
Alkamal01 wants to merge 2 commits into
lightningdevkit:mainfrom
Alkamal01:block-connection-logging

Conversation

@Alkamal01

Copy link
Copy Markdown
Contributor

Channelmanager: improve block connection logging

Fixes#2348. Supersedes #4420.

best_block_updated was logging at TRACE, making it impossible to track chain tip progress without enabling full trace logging. This upgrades it to INFO.

Also adds per-txid DEBUG logs in transactions_confirmed so individual transactions triggering channel updates are visible at a useful log level.

The original PR #4420 also added an INFO log in filtered_block_connected, but that duplicates the one in best_block_updated (which filtered_block_connected calls directly). That log is left out here.

Upgrade best_block_updated log from TRACE to INFO so chain tip
updates are visible without enabling full trace logging.
Add per-txid DEBUG logs in transactions_confirmed to make it easier
to identify which transactions triggered channel updates.
@ldk-reviews-bot

ldk-reviews-bot commented May 2, 2026

Copy link
Copy Markdown

I've assigned @valentinewallace 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.

Comment on lines +15971 to +15973
for (_, tx) in txdata.iter() {
log_debug!(self.logger, "Confirmed transaction {} in block {} at height {}", tx.compute_txid(), block_hash, height);
}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

compute_txid() performs a double-SHA256 over the serialized transaction, and the log_given_level! macro evaluates its arguments unconditionally (the level check is inside the Logger::log implementation, not before argument evaluation). This means the loop runs and hashes every transaction even when the logger's level is above DEBUG.

Consider either:

  1. Guarding the loop behind a level check, or
  2. Folding these per-txid details into the existing TRACE log, or
  3. Using a lazy wrapper (e.g., a Display impl that computes on fmt) — though this still wouldn't avoid the loop itself.

While txdata only contains matching transactions (not the full block), computing txids unconditionally on every block connection is unnecessary overhead for users who don't have DEBUG enabled.

@ldk-claude-review-bot

ldk-claude-review-bot commented May 2, 2026

Copy link
Copy Markdown
Collaborator

Both prior issues are resolved in the latest commit:

  1. Transaction type path (prior comment on line 15971): Fixed — now uses Transaction directly (in scope from line 24) instead of the private chain::transaction::Transaction path.

  2. Unconditional compute_txid() (prior comment on line 15979): Fixed — the LazyTxid wrapper defers compute_txid() to the Display::fmt implementation. Since format_args! captures a reference to LazyTxid without invoking Display::fmt, and the Logger::log method only formats the message when the level check passes, the double-SHA256 is only computed when DEBUG logging is actually enabled.

No new issues found. The code is clean.

No issues found.

Both previously flagged issues have been addressed in the latest commit (985a82bb):

  • The Transaction type reference now uses the in-scope import instead of a private module path.
  • compute_txid() is correctly deferred via the LazyTxidDisplay wrapper, avoiding unnecessary hashing when DEBUG is disabled.

@codecov

codecovBot commented May 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.16%. Comparing base (6573d42) to head (985a82b).
⚠️ Report is 215 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #4586 +/- ##
==========================================
+ Coverage 86.99% 87.16% +0.17% 
==========================================
Files 163 161 -2 Lines 109008 109266 +258 Branches 109008 109266 +258 ==========================================
+ Hits 94828 95247 +419 + Misses 11696 11544 -152 + Partials 2484 2475 -9 
FlagCoverage Δ
fuzzing?
fuzzing-fake-hashes31.21% <100.00%> (?)
fuzzing-real-hashes22.94% <100.00%> (?)
tests86.23% <100.00%> (+0.13%)⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadlightning/src/ln/channelmanager.rs Outdated

let block_hash = header.block_hash();
log_trace!(self.logger, "{} transactions included in block {} at height {} provided", txdata.len(), block_hash, height);
struct LazyTxid<'a>(&'a chain::transaction::Transaction);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

chain::transaction::Transaction references a private import — chain/transaction.rs has use bitcoin::transaction::Transaction; (no pub), so this name is not accessible from outside that module. This should fail to compile with error[E0603]: import 'Transaction' is private.

Transaction is already imported at line 24 of this file via use bitcoin::transaction::Transaction;, so the fix is simply:

Suggested change
structLazyTxid<'a>(&'achain::transaction::Transaction);
structLazyTxid<'a>(&'aTransaction);

…gging
Use a lazy Display wrapper to format confirmed txids, preventing unconditional hashing when DEBUG logging is disabled.
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! 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.

@valentinewallace

Copy link
Copy Markdown
Contributor

Superseded by #4659

@TheBlueMatt

Copy link
Copy Markdown
Collaborator

reopening per #4659 (comment)

@TheBlueMattTheBlueMatt reopened this Jun 9, 2026
@kamal-ogtl

Copy link
Copy Markdown

reopening per #4659 (comment)

Thanks for reopening!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve block connection logging

6 participants

@Alkamal01@ldk-reviews-bot@ldk-claude-review-bot@valentinewallace@TheBlueMatt@kamal-ogtl