Skip to content

v0.1.2 — Startup status and diagnostics

Choose a tag to compare

@StormAvenger StormAvenger released this 28 Oct 13:48
· 18 commits to main since this release

Buzz now shows useful startup feedback instead of an unexplained black desktop, with GPU availability and a private diagnostic download in the top bar.

  • Startup and reconnection guidance waits for the real Buzz window and desktop connection, with a Retry connection button when delayed.
  • GPU status runs a small CUDA computation and Faster Whisper compatibility check once per start. It also reflects Buzz’s Force CPU setting; it does not track individual jobs’ GPU use.
  • Diagnostics downloads an allowlisted JSON report locally. It excludes raw logs, recordings, transcripts, credentials, environment dumps, private paths, hostnames, IP addresses, and GPU identifiers. Nothing is uploaded automatically.
  • Frequent status updates use shared memory. Status polls do not create access-log writes. Existing storage mappings and GPU dependencies are unchanged.

The tested source is commit 77aa07c. All 20 Python tests, both JavaScript tests, and the Linux build and container checks passed, including actual shared-memory placement and the live status endpoint. Browser checks covered startup/recovery, GTX 1080 GPU availability, and the downloaded diagnostic schema.

Published image: ghcr.io/stormavenger/buzz-unraid:0.1.2 and stable :latest. Both tags are publicly available without a registry login.

Digest: sha256:7d6145072827bb5fe3293d7e7d46d2faceedc4c9d3a7b68433eaa40a8cec3ec5.

The publication workflow passed every gate. The scan reports zero HIGH or CRITICAL findings; 645 MEDIUM and 32 LOW findings remain visible in the attached report. Matching-source collection completed with 1,064 archives and zero failures. All 14 uploaded release assets are present, and their reported digests match SHA256SUMS. See SOURCE-README.txt for source archive instructions.

Browser microphone forwarding remains unconfigured. Automatic import after upload and expanded job-status controls are saved for a later release.

Archived validation details

Moved from docs/VALIDATION.md on October 28, 2026. These are historical results for this release.

Runtime commit 55657a92003ffc0f096f72cdb7446a0886cabea9 passed the Linux build and container checks: source/privacy checks, 20 Python tests, two JavaScript diagnostic-schema tests, Compose validation, build-context exclusion, actual Qt readiness, and HTTP/storage/restart smoke checks. The publication results for the matching release are recorded below.

A disposable Unraid container built over v0.1.1 with the new status code and original pinned GUI assets showed the startup screen and then the live Buzz desktop. The GTX 1080 passed the new small CUDA computation and Faster Whisper capability probe, and the toolbar displayed GPU available. A browser diagnostic download contained only the declared version/status/event schema. A simulated paused application event loop triggered delayed-start guidance and the retry button; retry reconnected the browser, and the screen recovered automatically after the application resumed. No personal recordings, production appdata, or production container were used for these tests.

The follow-up runtime commit 77aa07c1304ff551973d6f8b7b702a9c4f359c55 passed the Linux build and container checks. It moves both status files to /dev/shm/buzz-status and suppresses access-log entries for status polls. The smoke test confirms both files reside on the shared-memory tmpfs and the status endpoint still works. The manual publication default is now 0.1.2.

The v0.1.2 publication workflow passed all build, runtime, privacy, inventory, scan, source-collection, asset-upload, and image-publication gates at release commit 77aa07c1304ff551973d6f8b7b702a9c4f359c55. The scan reports zero HIGH or CRITICAL findings, with 645 MEDIUM and 32 LOW findings retained. Matching-source collection completed with 1,064 archives and no failures. All 14 uploaded assets are present, and GitHub's reported asset digests match the release checksums. The scan, source-manifest, and image-label files were also downloaded anonymously and checked against SHA256SUMS.

Both public image tags :0.1.2 and :latest resolve anonymously to sha256:7d6145072827bb5fe3293d7e7d46d2faceedc4c9d3a7b68433eaa40a8cec3ec5.

An anonymous pull with an empty Docker credential configuration succeeded on Unraid and matched that digest. The exact published image passed CUDA computation and offline Faster Whisper Small inference of the public speech sample on the GTX 1080. A fresh disposable desktop became healthy, reported version 0.1.2 and the release revision, and showed GPU available in Chrome. Its live status endpoint and both shared-memory files passed placement/readiness checks. A diagnostic report downloaded from that released interface contained only the intended version/status/event schema. The disposable containers and anonymous data volumes were removed after verification; the user's installed application was not updated or recreated.