Skip to content

bug: DCC connectable status should look at different property #167

@bitglows

Description

@bitglows

DCC shows "Not Connectable" which is falsely reported by the DCC API in the status endpoint (first call).
However, the second call (/api/v1/users/...) has a property unconnectable which is reported correctly. So should probably take that instead of the first one.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions