46af2f0632
.forgejo/workflows/check.yml runs on every push to main/v1 (+ manual dispatch): nix flake check --no-build (full module-system eval incl. the downstream template through mkFlake), py_compile of nomarchy-theme-sync, and bash -n over tracked .sh files. The always-on net under direct-to-main pushes — first slice of the ROADMAP lock-bump CI item. Scoped to the eval tier deliberately: the instance's runner is an act_runner docker container (no systemd, no /dev/kvm — established from the legacy repo's .gitea/workflows/check.yml, which ran 57 times on it), so the checks.* VM suite and real builds can't run there. A commented vm-checks job documents the KVM-runner upgrade path; the legacy workflow's container gotchas (nixbld setup for the single-user installer, sandbox=false for Stylix IFD, Nix pinned 2.31.5 vs lazy-trees, no JS actions past node20) are carried over verbatim in the header. docs/TESTING.md §1b documents what a green run does and does not mean. Verified: V0 locally (the same check commands, minus the container Nix install) + YAML parse. A real green run depends on the runner still being registered — not API-visible unauthenticated, so that is queued as [human] BACKLOG item 20. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
67 lines
3.7 KiB
Markdown
67 lines
3.7 KiB
Markdown
# Memory — durable lessons, learned the hard way
|
|
|
|
Curated, not append-only: one line per fact, newest at the top of its
|
|
section; delete entries that stop being true. Details usually live in a
|
|
docs/ROADMAP.md decision record — pointer given as (§ item). Add a fact
|
|
here the moment a debugging session teaches you something a future
|
|
iteration would otherwise rediscover.
|
|
|
|
## Testing & VM recipes
|
|
- CI (`.forgejo/workflows/check.yml`) is **eval-tier only**: the Forgejo
|
|
act_runner is a docker container (no systemd, no /dev/kvm). Container
|
|
gotchas are documented in the workflow header (single-user Nix +
|
|
nixbld users, `sandbox=false` for Stylix IFD, Nix pinned 2.31.5 vs
|
|
lazy-trees, no JS actions past node20) — learned over the legacy
|
|
repo's 57 runs; read them before touching the workflow.
|
|
- Reusable headless VM harness: `checks.*` via runNixOSTest — existing
|
|
examples to crib from: `distro-id` (boots + `switch-to-configuration
|
|
dry-activate`), `hardware-toggles` (kernel cmdline/PAM assertions),
|
|
`battery-charge-limit` (fake Mains adapter via `test_power`, real udev
|
|
uevent, `InvocationID` change proves the restart).
|
|
- Themed-desktop screenshots work headlessly: software-GL Hyprland
|
|
(`LIBGL_ALWAYS_SOFTWARE` on virtio-gpu) + `machine.screenshot()` QMP
|
|
dump — prototyped 2026-06-19, kept as the fallback for theme previews
|
|
(§ Visual theme picker).
|
|
- Hyprland/Ghostty need guest GL (`virtio-vga-gl`, `gl=on`) in
|
|
interactive QEMU or the session won't start; black screen ≈ missing GL
|
|
(docs/TESTING.md § gotchas).
|
|
- No KVM = slow, not broken; don't read slowness as failure.
|
|
|
|
## Known-broken / watchlist
|
|
- **btrfs-assistant 2.2 segfaults on launch** (nixpkgs 26.05,
|
|
`libbtrfsutil.so.1.4.0` ABI mismatch; crashes on hardware too, not a VM
|
|
artifact). `nomarchy-snapshots` fzf flow is the shipped fallback;
|
|
re-check on every lock bump (§ Snapshot browse/restore; BACKLOG NOW#2).
|
|
- **NixOS release bump is a trap:** the discarded attempt
|
|
(branch deleted 2026-06-22) hit a Hyprland OOM blocker; a redo is a
|
|
deliberate `v2`, never part of routine lock bumps.
|
|
- `theme-state.json` is git-tracked inside an 86 MB flake tree, so every
|
|
state write re-copies the source before eval — the wallpapers-artifact
|
|
split (BACKLOG LATER) is the decided fix (§ Faster switches).
|
|
|
|
## Gotchas (cost a debugging session once)
|
|
- Never kill a Wayland session-lock client (hyprlock): its crash
|
|
failsafe drops to a tty instead of unlocking (§ Hibernate
|
|
double-unlock).
|
|
- rofi `element-icon size` is one value = a square cell; `WxH` silently
|
|
collapses and non-square icons letterbox — pre-crop images square at
|
|
build (§ Visual theme picker).
|
|
- WirePlumber 0.5 monitor rules can only early-match `device.api`;
|
|
`device.product.name` etc. bind *after* the rule runs — surgical
|
|
libcamera scoping is impossible (§ Webcam).
|
|
- `hyprctl switchxkblayout` is a *global* layout flip; per-device isolation
|
|
needs `device[<name>]:kb_layout` keywords (§ Keyboard layouts).
|
|
- Waybar's clock captures the timezone at construction — a zone change
|
|
needs SIGUSR2 (watcher in `timezone.nix`) (§ Automatic timezone).
|
|
- Waybar `persistent_workspaces` (underscore) is dead syntax silently
|
|
ignored; the hyphen form is honoured and renders phantom workspaces
|
|
(§ Waybar shows non-existent workspaces).
|
|
- GTK4/libadwaita/Qt6 read light/dark from the portal's
|
|
`org.freedesktop.appearance color-scheme` (dconf), not Stylix polarity
|
|
(§ GTK/Qt ignore the theme's mode).
|
|
- Update order matters downstream: `sys-update` (lock) before
|
|
`home-update`, or desktop changes are silently skipped against the old
|
|
lock (README § 3).
|
|
- grub `loadfont`s every `.pf2` in a theme dir — reuse a bundled DejaVu
|
|
rather than shipping fonts (§ Distro branding).
|