zwave-js / zwave-js-ui / 19592492104

20%

Build Type

push

github

Committed by web-flow

Commit Message

feat: add wizard to collect debug information (#4460)

## Debug Package Collection ✅

Complete debugging package wizard implementation.

**Backend:** DRY DebugManager, async pathExists, logContainer
encapsulated, WebSocket session status, UI/driver logs (even when
disabled), proper cleanup

**Frontend:** App.vue global access, topbar button, app.confirm dialogs,
device chips with full names (manufacturer + product), session
persistence, 500ms loading delay

**Workflow:** Topbar→Start→Active→Topbar→Devices→ZIP, persists across
refreshes

**API:** POST /api/debug/start, POST /api/debug/stop, POST
/api/debug/cancel

**Features:** Global topbar access, Pinia+WebSocket state, auto debug
levels, file-based capture, logs captured when disabled, chips
(mfr+product+name), ZIP (logs+dumps+metadata), session persistence,
smart loading

**Technical:** Winston FileTransport (silent-independent),
Driver.updateLogConfig(), createDump(), Archiver, WebSocket INIT, Pinia,
Vue3/Vuetify3, pathExists, store/.debug-temp/, cleanup

**Security:** Auth required, rate limiting, no sensitive data, proper
cleanup, isolated temp directory

**Quality:** DRY principles, import best practices, UI consistency,
Vue3/Vuetify3, clean async/await

**Tests:** Logger tests updated for transport-level silent flags

Fixes zwave-js/zwave-js-ui#4213

<!-- START COPILOT CODING AGENT SUFFIX -->



<details>

<summary>Original prompt</summary>

> 
> ----
> 
> *This section details on the original issue you should resolve*
> 
> <issue_title>Add helper/wizard/... to collect debugging
package</issue_title>
> <issue_description>No matter how much we document, provide videos and
automatically share links to the correct procedure of creating logs,
some users still are not capable of following those instructions and
provide the wrong logs, on the wrong loglevel, etc.
> Even if they do, they often upload a 24h logfile with hundreds of
thousands of lines (which is fine), but often forget to mention the
ti... (continued)

Run Details

334 of 443 branches covered (75.4%)

Branch coverage included in aggregate %.

5 of 489 new or added lines in 6 files covered. (1.02%)

1 existing line in 1 file now uncovered.

4052 of 21875 relevant lines covered (18.52%)

1.15 hits per line