Skip to content

[bug]: Scale Timeout for Block Consumers based on more contraints and data #10407

@ziggie1984

Description

@ziggie1984

Pre-Submission Checklist

  • I have searched the existing issues and believe this is a new bug.
  • I am not asking a question about how to use lnd, but reporting a bug (otherwise open a discussion).

LND Version

master

LND Configuration

Backend Version

Backend Configuration

OS/Distribution

Bug Details & Steps to Reproduce

See also lightninglabs/taproot-assets#1890, in the logs there are quite some occurrences of the following error:

2025-11-30 23:01:45.519 [ERR] CHIO: Height[925878]: Failed to process block: consumer TxPublisher: process block timeout

Currently we use very simple timeouts for all consumers equally and for example do not take the number of closed channels into account. We need a more refined logic so we do not run into a timeout when a longer processing time is expected.

Expected Behavior

Debug Information

No response

Environment

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockbeatIssues related to chainiobugUnintended code behaviour

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions