Skip to content

Stop completing monitor udpate completion actions when claiming on a closed channel #2355

Closed

Description

@TheBlueMatt

Remove this hunk and track them globally:

        // Note that we do process the completion action here. This totally could be a
        // duplicate claim, but we have no way of knowing without interrogating the
        // `ChannelMonitor` we've provided the above update to. Instead, note that `Event`s are
        // generally always allowed to be duplicative (and it's specifically noted in
        // `PaymentForwarded`).
        self.handle_monitor_update_completion_actions(completion_action(None));

Activity

  1. added this to the 0.0.117 milestone on Jun 14, 2023
  2. modified the milestones: 0.0.117, 0.0.118 on Sep 13, 2023
  3. TheBlueMatt commented on Sep 13, 2023

    @TheBlueMatt
    CollaboratorAuthor

    Slipping this, the documentation updates in #2562 explicitly state that the async mode is not yet fully supported, which is a reference to this and one other issue involving MPP claims across channels hitting tail latency implying loss of preimage on one channel before other channels hit disk.

  4. modified the milestones: 0.0.118, 0.0.119 on Oct 12, 2023
  5. added a commit that references this issue on Aug 2, 2025
    a18b2c9
  6. TheBlueMatt commented on Aug 2, 2025

    @TheBlueMatt
    CollaboratorAuthor

    Really fixed by #3414.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions