Auto-sync: 2026-10-08

This commit is contained in:
Dominik Schön
2026-10-08 22:00:16 +00:00
parent 8dca234bc6
commit b8d38c5640
13 changed files with 805 additions and 3 deletions
+3
View File
@@ -14,6 +14,7 @@ The entry records WHAT changed, WHY, and WHETHER it helped (if validated).
```
| Date | Skill | Change Type | Description | Validation | Outcome | Ref |
```
| 2026-10-08 | smart-home-automation | adopted | EMHASS-References erweitert: Status-Block in defect-analysis (Pointer-Datei) + neue Sektion "CSV Laws & Shadow Testing" in api-and-config | tested | accepted | docs/solutions/workflows/2026-10-08-emhass-phase2-shadow-methodology.md |
- **Change Type**: `created` | `patched` | `deleted` | `adopted`
- **Validation**: How was success measured? (`manual` | `tested` | `benchmark` | `n/a`)
@@ -38,3 +39,5 @@ The entry records WHAT changed, WHY, and WHETHER it helped (if validated).
`validation: manual` — they may enable future improvements.
- **Rollbacks** are explicitly tracked — if a skill patch caused regressions and was
reverted, the entry stays with `outcome: rolled-back`.
| 2026-10-08 | smart-home | patched | NUT-Absatz ergänzt: Kaskade, Master/slaves, roh-Proto-Details, Watchdog-Cron 4cbf03ccb4de | tested | accepted | docs/solutions/bug-fixes/2026-10-07-nut-ups-ms-a2-1-deployment.md |
| 2026-10-08 | (none) | adopted | PAT-015 systemd-path-blindness erstellt (Exit-127-Klasse: ~/.local/bin unsichtbar im Service-PATH; trap-EXIT-Cleanup-Pflicht) | tested | accepted | docs/solutions/bug-fixes/2026-10-08-hermes-offsite-backup-aws-path-rca.md |
+42
View File
@@ -0,0 +1,42 @@
# Skill Impact Tracker
> Inspired by WikiSkill (arXiv:2608.27454) — tracks skill modifications, their validation
> outcomes, and acceptance decisions. Prevents repeating failed modifications and provides
> an audit trail of skill evolution.
## How to Use
When a skill is patched, created, or deleted, append an entry to the table below.
The entry records WHAT changed, WHY, and WHETHER it helped (if validated).
### Entry Format
```
| Date | Skill | Change Type | Description | Validation | Outcome | Ref |
```
- **Change Type**: `created` | `patched` | `deleted` | `adopted`
- **Validation**: How was success measured? (`manual` | `tested` | `benchmark` | `n/a`)
- **Outcome**: `accepted` | `rejected` | `rolled-back` | `pending`
- **Ref**: Session ID or solution doc path
## Audit Trail
| Date | Skill | Change Type | Description | Validation | Outcome | Ref |
|------|-------|-------------|-------------|------------|---------|-----|
| 2026-08-30 | compound-learning | patched | Added WikiMaintainer phase + patterns/ guidance from WikiSkill paper analysis | tested | accepted | this session |
| 2026-08-30 | (retrospective) | created | 4 solution docs + 2 new patterns (PAT-008, PAT-009) from 30-day retrospective | tested | accepted | this session |
| 2026-08-13 | hindsight | patched | Expanded meta-memory automation table (decay scoring, drift detection, skill health) | tested | accepted | session 2026-08-13 |
| 2026-08-13 | (3 cron jobs) | created | Decay scoring, drift detection, skill health check — no_agent cron jobs | tested | accepted | session 2026-08-13 |
## Notes
- **Rejected proposals persist here** — they are NOT deleted. Future skill updates can
consult this log to avoid repeating failed approaches (the WikiSkill paper showed this
is critical for effective evolution).
- **Neutral changes** (no improvement, no regression) are recorded as `accepted` with
`validation: manual` — they may enable future improvements.
- **Rollbacks** are explicitly tracked — if a skill patch caused regressions and was
reverted, the entry stays with `outcome: rolled-back`.
| 2026-10-08 | smart-home | patched | NUT-Absatz ergänzt: Kaskade, Master/slaves, roh-Proto-Details, Watchdog-Cron 4cbf03ccb4de | tested | accepted | docs/solutions/bug-fixes/2026-10-07-nut-ups-ms-a2-1-deployment.md |
| 2026-10-08 | (none) | adopted | PAT-015 systemd-path-blindness erstellt (Exit-127-Klasse: ~/.local/bin unsichtbar im Service-PATH; trap-EXIT-Cleanup-Pflicht) | tested | accepted | docs/solutions/bug-fixes/2026-10-08-hermes-offsite-backup-aws-path-rca.md |
+49
View File
@@ -0,0 +1,49 @@
---
pattern_id: PAT-015
title: "systemd-PATH-Blindness: binaries aus ~/.local/bin verschwinden im Service-Kontext"
category: infrastructure
severity: high
status: active
first_observed: 2026-10
last_updated: 2026-10-08
related_systems: [hermes-agent-01, systemd]
related_solution_docs: [docs/solutions/bug-fixes/2026-10-08-hermes-offsite-backup-aws-path-rca.md]
related_skills: []
---
# PAT-015 — systemd-PATH-Blindness
**Trigger**: Ein Skript, das interaktiv/per SSH fehlerfrei läuft, stirbt als systemd-Service mit
`command not found` (Exit 127) — typischerweise bei pip-user-installierten CLIs (`aws`, `uv`),
Node/npm-Tools oder allem unter `$HOME/.local/bin`, `$HOME/.cargo/bin`, `/opt/*`.
## Symptom
- Journal: `<script>: line NN: aws: command not found` → `status=127`
- Dieselbe Binary funktioniert problemlos in der interaktiven Shell desselben Users.
- Bei `set -e`-Skripten mit Cleanup AM ENDE: sekundär Müll-Akkumulation, weil der Exit
vor dem Aufräumschritt liegt.
## Root Cause
systemd startet Units mit definiertem Minimal-PATH (`/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin`),
OHNE die User-Shell-Profile zu sourcen. Pip `--user`-Installationen landen in `~/.local/bin`,
das nur via `~/.profile`/shell-Init in PATH kommt. Interaktiv≠Serviceland.
## Mitigation
1. **Robuste Variante (im Skript):** Absolutpfad mit Fallback-Kette:
`BIN="$(command -v foo || true)"; [ -z "$BIN" ] && BIN="/home/user/.local/bin/foo"; [ -x "$BIN" ] || exit 1`
2. **Unit-seitig:** Drop-in `Environment="PATH=/home/user/.local/bin:$PFAD"` — macht ALLE
Scripts der Unit robust, auch solche Dritter.
3. **Cleanup-Traps:** `trap 'rm -f "$TMPFILE"' EXIT` — garantiert Aufräumen bei JEDEM Exit,
egal wo `set -e` zuschlägt.
## Prevention
- Beim Schreiben neuer systemd-Units mit User-Skripten: PATH-Annahme niemals erben lassen.
- Watchdog-Muster: Backup-Jobs brauchen Alter-des-letzten-Erfolgs-Monitoring (still sterbende
Jobs bleiben sonst Wochen unsichtbar — hier 10+ Tage TOOT).
- Bei Exit-127 im Journal zuerst PATH-Differenz interaktiv vs. Service prüfen (`systemctl show -p Environment`).
## Evidence
- 2026-10-08: hermes-backup.service (backup-to-s3.sh, täglich 04:00 UTC) Exit 127 seit ≥27.09.,
10× ~2G-Tarballs in /tmp bis Root-FS 100 %. Fix: Skript-AWS_BIN + Drop-in-PATH + trap.
Verifikation: Produktionslauf SUCCESS + S3-Readback 2.284.533.218 B.
→ docs/solutions/bug-fixes/2026-10-08-hermes-offsite-backup-aws-path-rca.md