Skip to content

Syspeek 0.11.1

Choose a tag to compare

@github-actions github-actions released this 01 Nov 06:39
· 476 commits to main since this release

Syspeek 0.11.1 — two fixes for problems hit on a real machine

"HUD already running" when nothing was on screen.
The single-instance gate keyed on the user alone, so a HUD running on any
display held the lock for every later launch — a nested server, an Xvfb, a
second seat, or an instance you had forgotten about. The refusal named neither
the display nor the process, and there was no way past it.

  • The lock is now per session: <user>-<platform>_<display>, derived from the
    platform the app will actually use (so an X11 session with a leftover
    WAYLAND_DISPLAY no longer collides two X displays).
  • The refusal names what holds it: a HUD is already running on DISPLAY :99 (pid 996796).
  • syspeek --new-instance starts one anyway.

syspeek update failing with "install a downloader manually".
The real error was a write failure — the bundle was going into /tmp, which is
a tmpfs on most desktops, and on the machine that reported this it was 82% full
(wget: short write: Disk quota exceeded). The installer could not tell "no
downloader" from "the disk is full", so it recommended apt-get install curl
to someone who has curl, and asked for a sudo password to retry a download that
could not succeed.

  • Downloads go to real disk now (SYSPEEK_TMPDIR → $XDG_CACHE_HOME → $HOME →
    TMPDIR → /tmp), on Linux, macOS and Windows.
  • A write failure stops the ladder immediately and says so, with the free space
    of the directory and the XDG_CACHE_HOME escape.
  • The package-manager rescue only runs when there is no downloader at all, and
    the final message quotes the last real error and what was tried.

Test hermeticity. The Windows fake-CLI cases could lose a race with the real
aws.exe on the image and fail intermittently; the provider options now carry a
cliPath so a test — or an operator with two aws installs — can pin the binary
instead of trusting PATH.

Also: the README claimed a "27-page console" in one place and "32-view" in
another. The list is now the rail order and matches the 32 rows the tests pin.

Nothing else changed; 14/14 tests on Linux, macOS, Windows, and both clean-room
Debian/Ubuntu container builds.