Skip to content

[Bug]: backend.log is listed in Settings but cannot be read there #377

Closed

Description

@thcp

What happens

Settings → Logs → Location lists backend.log ("Desktop only: raw output of
the bundled Python backend process") along with its two rotations, and
/api/logs.zip ships them. But the sub-tabs offer only Application log and
Setup log — _LOG_VIEWS has no backend entry.

So the file is advertised in the UI and downloadable, yet unreadable in the app.

Why it matters

backend.log holds what stemdeck.log cannot: anything the process printed
before logging was configured, and anything that killed it before a handler
ran. A backend that dies at startup leaves stemdeck.log empty and the answer
in backend.log — the one log you cannot open.

setup.log is equally desktop-only and does have a tab, so this is an
inconsistency as much as a gap.

Expected

A "Backend log" tab beside the other two, reading backend.log and its
rotations through the same windowed tail endpoint.

Activity

  1. added
    bugSomething isn't working
    observabilityLogging, monitoring, diagnosability
    on Aug 16, 2026
  2. thcp commented on Aug 16, 2026

    @thcp
    CollaboratorAuthor

    Fixed in #372 (2c3541d). Added a "Backend log" tab plus a backend entry in _LOG_VIEWS covering backend.log and its rotations. A test now walks _LOG_FILES against _LOG_VIEWS and fails if a file the Settings pane advertises has no view to read it in.

  3. self-assigned this
    on Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingobservabilityLogging, monitoring, diagnosability

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions