night 2026-10-22: the seven 15:47 rulings in effect or ready (D6, D8 live; D21 waits for controller 0.340.0; D3/D5 website patch; D4 two patches); data-loss candidates proven/fixed/filed; R-1214 cause + capped copy proven on 9202; R-1204 alarm built; repos-private read; STATUS morning list + D29/D30/D31; CONTEXT; 03/05/07/09; rows 178 -> 180 (opened R-1218..R-1222, closed R-206, R-992, R-1207)
gates / gates (push) Successful in 16m7s
gates / gates (push) Successful in 16m7s
This commit is contained in:
admin committed
1 parent
1100a344d5
commit
acc78637d9
20 files changed
+413
-34
No files matched your search
@@ -2,7 +2,7 @@
|
||||
|
||||
**Ready for Tester 2? Yes — tell the friend go (hand-over list: `documentation/pilot/TESTER2-handover.md`).**
|
||||
|
||||
**Updated 2026-10-22 (day).** A rebuilt box no longer overwrites the family's saved mail list (hub 0.165.0, controller 0.339.0); demo-felhom's own list, replaced this morning, is back. The swap warning now fires only when a machine has clearly too little swap (your D28 = A).
|
||||
**Updated 2026-10-22 (night).** Your seven picks of 15:47 are in effect or ready: D6 and D8 are live, D21 waits for the controller release, and D3, D5 (the website) and D4 (root SSH) are ready patches. Four controller fixes are built and proven on the scratch box, among them a gentler night copy (the 03:30 memory pressure) and no import over a stopped app. Nothing was released or deployed; the morning list below has the order.
|
||||
|
||||
## What works
|
||||
- A box installs from nothing with the public installer, links to the hub, and moves to the floor by itself (map A1, A3, A4).
|
||||
@@ -16,10 +16,9 @@
|
||||
|
||||
## What is broken
|
||||
- **P1:** about 12 homelab logins still use a password that was public, and the public Gitea repo is not decided (R-925, yours).
|
||||
- Two root-level weaknesses wait on your decisions D3 and D4 (R-985, R-982).
|
||||
- Tester 2 is off since 2026-10-04: old emergency password, no off-site check, no bootstrap (R-1139, R-1104, R-862).
|
||||
- DooPlex: the failed disk is still in the box, its alarms silenced (R-934); something sets the shared checkout to „bare" (R-935).
|
||||
- The scratch box cannot use agent features (R-1083) or read the drill catalog (R-992).
|
||||
- The scratch box cannot use agent features (R-1083).
|
||||
|
||||
## What we work on
|
||||
- Dated checks, run by CC. 2026-10-23: no app stop when the host is busy (R-1173). 2026-10-26: each hub daily job ran once on the clock-change day (R-1183). 2026-10-27: the weekly clean-up window (R-435; the logs of the last one were lost to restarts).
|
||||
@@ -30,15 +29,11 @@ Newest first. CC's pick is in the „Pick" column. Each row also has its full te
|
||||
|
||||
| # | Row | Question | Pick (why) | The other option costs | If you do nothing | Blocked |
|
||||
|---|---|---|---|---|---|---|
|
||||
| D27 | R-1207 | A host with no swap gets nothing from the swap fix, and the agent never adds swap. Add host swap automatically (BYO too), or refuse an 8 GB host without swap at install? | **Report only for now** (our installer gives 7.75 GB, and Tester 2's laptop used our installer; the alarm and the install-page sentence now tell you) — decide after the first BYO box | Add it: the agent changes a disk its owner set up; refuse: a BYO household cannot start | a no-swap host can still freeze; you get the alarm | — |
|
||||
| D21 | R-49 | Immich's off-site copy: leave out only the AI model files now (B), or also the raw database folder and Immich's own backups (A)? | **B now** (−62 %, no new risk); A's other parts after their proof | A: −92 %, but it needs a restore path we have never run | every Immich box sends about 12 times its real data off-site each night | — |
|
||||
| D31 | R-1205 | After a box death, a second install that is deleted before it makes a key stops the automatic re-issue of the whole-box copy. Let the hub skip such a deletion, or keep your manual press? | **Skip it** (that install held no key, so nothing is lost — the same reasoning the key carry uses) | Keep the press: you get a mail and press „Re-issue PBS credentials” each time | that household gets no whole-box copy until you press | — |
|
||||
| D30 | R-1204 | After a box ran with its clock ahead, how does its tunnel to ep0 heal? | **The agent makes a new key and registers it** (the peer path that exists; nothing new on ep0) | ep0 removes and re-adds the peer on a hub-signed request: a new write path on ep0 | with hub 0.166.0 you get the alarm, and the repair is by hand on ep0 | the tunnel fix |
|
||||
| D29 | R-925 | Make the controller's repository private now? (felhom.eu, the agent and the catalog must stay public: the website, every install and every box read them with no login.) | **No, not now** (its image stays public anyway, and the no-secret gate is the control; look again when felhom.eu can go private) | Yes: a read token in CI for every repo that clones it, one more secret to keep | nothing changes | — |
|
||||
| D9 | R-1062 | Split the N100's USB drive in two, for multi-drive tests? | **No — keep one drive** (the lived-in box keeps its nightly whole-box backup) | Split: the box loses its local whole-box backup, or you buy a second drive first | it stays one drive; multi-drive tests stay on Tester 1 | — |
|
||||
| D8 | R-206 | Install DooPlex's Docker settings from git (Docker restarts once), with a weekly build-cache prune? | **Yes, in a quiet window** (a rebuilt DooPlex then keeps the settings) | No: the live settings stay hand-made, and a rebuild loses them | git and the host can drift apart | — |
|
||||
| D7 | R-990, R-989 | Rule on the forum ideas and the selfh.st ideas now, or park them? | **Park them** (P4; nothing waits on them) | Rule now: about one hour of reading | nothing changes; the research gets old | — |
|
||||
| D6 | R-992 | The scratch box cannot read the private drill catalog: give it a read-only login, or make that copy public? | **A read-only login** (the drill catalog stays private) | Public copy: anyone can read the drill catalog | every new-app test needs staging by hand | new-app tests |
|
||||
| D5 | R-991 | Approve the minimum machine: x86-64, 4 cores, 8 GB RAM, 256 GB SSD (recommended: 16 GB, 512 GB)? | **Approve** (measured on the N100 with 61 apps) — the 8 GB freeze of 2026-10-20 is fixed by agent 0.162.0 (11 h soak on a fresh 8 GB box, no freeze) | Change it: one edit | no hardware page; a buyer with a Raspberry Pi can still download the installer | the hardware page |
|
||||
| D4 | R-982 | Stop root SSH with a password from the household network (key only)? | **Yes — key only** (the password stays for the console) | Keep it: anyone on the household network can try the password | the host keeps accepting root password logins from the LAN | — |
|
||||
| D3 | R-985 | Our „zero-knowledge" wording is stronger than the product: change the wording, or remove the operator's root reach to the key? | **Change the wording now**; look again after the first sale | Remove the reach: a design change to break-glass | the website promises more than the product does | the website text |
|
||||
|
||||
## Waiting on you — do
|
||||
|
||||
@@ -51,8 +46,13 @@ Newest first. CC's pick is in the „Pick" column. Each row also has its full te
|
||||
6. BIOS: on the N100, read „After Power Loss"; on the HP, set „Bypass F1 Prompt on Configuration Changes" to Enable. Since 2026-10-14.
|
||||
7. Pin the first Facebook post (R-917), and look at the new cover in the Facebook phone app (R-919). Since 2026-10-12.
|
||||
|
||||
**Today, 2026-10-22.**
|
||||
1. Give Tester 2's friend the owner passphrase and the one-page guide, and tell him „go". The reset worked: his old copies are gone, nobody else's changed. If not: nothing happens; the link mail expires in 7 days (he can ask for a new one).
|
||||
**Morning, 2026-10-23 — in this order.**
|
||||
1. Publish the website patch: the D3 wording and the D5 hardware page (R-985, R-991). Say „publish”; CC pushes it. If not: the site keeps the stronger promise and has no hardware page.
|
||||
2. D4 rides two releases, both ready patches: the agent's config bundle (the next agent release, your vouch) and a new installer tag (R-982). Also press Discard on the hub's Hosts page for appliance 49 (tonight's test install). If not: hosts keep taking root passwords from the LAN.
|
||||
3. Deploy hub 0.166.0 (the clock-ahead tunnel alarm, built) and release the agent with its tunnel field, in the same agent release as item 2 (R-1204). If not: a dead tunnel stays silent.
|
||||
4. Release controller 0.340.0: Immich's model cache out of backups, no import over a stopped app, the catch-up checks, the capped night copy (R-49, R-1187, R-1189, R-1214). If not: these four wait.
|
||||
5. Decide D29 (a private repository) and 6. D30 (the tunnel repair), in the table above; D31 when you have time.
|
||||
7. Tester 2 (from 2026-10-22): give the friend the owner passphrase and the one-page guide, and say „go”. If not: the link mail expires in 7 days.
|
||||
**The rest**
|
||||
- Pull the failed disk Z6A07P2G out of DooPlex (R-934). If not: its alarms return on 11 November. Since 2026-10-12.
|
||||
- Rotate the reused homelab logins and decide the Gitea repo's visibility (R-925, P1). Since 2026-10-09.
|
||||
|
||||
Reference in new issue
Block a user