Skip to content

Peer actions: handle disconnect, ban, and unban failures in QML #66

Description

@johnny9

Code Gap

The QML peer details page exposes Disconnect and Ban actions, and the banned-peers page exposes Unban. The C++ model methods return success/failure, but the QML actions currently do not present success, failure, or recovery states to the user.

Visible peer-control actions should not silently fail for Preview/Beta.

Work Needed

  • Surface success/failure for peer disconnect, ban, and unban actions.
  • Disable or update actions when the selected peer disappears while the detail page is open.
  • Validate ban targets and durations before submitting the ban.
  • Refresh affected peer and ban-list state after each action.
  • Add coverage for successful disconnect, failed disconnect, successful ban, failed ban, successful unban, and failed unban.

Priority

Preview / P1 correctness bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingv1.0Required or tracked for v1.0 release

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions