Found on the deployment machine on 2026-10-11, the first time `hhstream-live` was run **as a unit** rather than from a login shell: a systemd unit's PATH has no system profile, so the capture command `grim` is not found, ten times, and the stream gives up. It answers on its port, serves the landing page and reports `"stopped": true, "failures": 10` while showing nothing -- the quiet half of the failure is what makes it worth a file. The module already solves this for `sessions.apps` by requiring an absolute store path; the stream's unit has to do the same (or set PATH, which is what made the deployment run work). Recorded in `docs/TODO/` with the two fixes, and named as a risk on stage 3 of the plan, which is the stage that turns this from an experiment into the only path.
36 lines
2.0 KiB
Markdown
36 lines
2.0 KiB
Markdown
# TODO
|
|
|
|
Known, unfixed problems — each one real, none of them guessed at.
|
|
|
|
Each file answers three questions and stops:
|
|
|
|
- **The issue** — what is actually wrong, with the evidence for it.
|
|
- **Ideas** — more than one, and which one is the recommended route.
|
|
- **Why it matters** — the impact, not the principle.
|
|
|
|
| item | severity | state |
|
|
| --- | --- | --- |
|
|
| [cursor-visibility-in-captures](cursor-visibility-in-captures.md) | high | answered: the compositor draws no cursor for a virtual pointer. Needs a decision on an overlay marker |
|
|
| [scroll-has-no-compositor-proof](scroll-has-no-compositor-proof.md) | medium | works live; unproven in a gate |
|
|
| [reconcile-while-containers-are-off](reconcile-while-containers-are-off.md) | medium | partly fixed: discovery now survives a restart; teardown still lives inside the feature |
|
|
| [kill-can-leave-the-app-alive](kill-can-leave-the-app-alive.md) | medium | found by counting windows, not sessions |
|
|
| [capture-binary-and-the-unit-path](capture-binary-and-the-unit-path.md) | medium | found the first time the app was run as a unit: a unit's `PATH` has no `grim` |
|
|
|
|
Closed since this folder was written:
|
|
|
|
- *"Containers do not bind"* — fixed. Windows are assigned by the pid the
|
|
compositor reports, moved onto their desk's workspace and read back. Two
|
|
sessions now hold two outputs with a real browser on each.
|
|
- *"The pointer is unusable while containers are off"* — fixed with it. The
|
|
pointer aims at the session's desk, and desks hold applications.
|
|
- *"Discovery refuses when two compositor instances exist"* — fixed. Each
|
|
candidate is asked for its version and the one that answers is used.
|
|
|
|
Severity here means "how much of the feature is actually delivered", not "how
|
|
loud the failure is". The highest is highest because a whole class of work is
|
|
blocked on it: the pointer is exact and invisible, so nothing can show *where*
|
|
anything happened.
|
|
|
|
When one of these is fixed, delete its file and the row — this folder is a list
|
|
of what is still true, not a history of what was thought.
|