Skip to content

CLI: high-priority Tor peers and redial entries are never cleaned up after a swap completes #1026

@binarybaron

Description

@binarybaron

swap/src/cli/event_loop.rs:546-553 registers a swap handler and then calls redial.add_peer(peer_id) and tor_priority_tracker.mark_high_priority(peer_id). None of these are ever removed — registered_swap_handlers has no .remove, and the pre-existing TODO on line 549 already notes the redial leak.

The CLI event loop has no swap-completion signal, so nothing triggers cleanup.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions