| Age | Commit message (Collapse) | Author |
|---|
|
- fish_frozen_key_bindings.fish: migrate fish_key_bindings to global scope
- fish_frozen_theme.fish: migrate syntax highlighting theme to global scope
- gemtexter.fish: add gemtexter publish functions
- tmux.conf: enable extended-keys for modern terminal key handling
|
|
|
|
Mirrors the default Prefix+( / Prefix+) bindings but filtered to
sessions whose name starts with the 'A-' agent-workload prefix.
Logic lives in scripts/tmux-cycle-a-session.
Amp-Thread-ID: https://ampcode.com/threads/T-019e7daf-7dbc-720d-a818-d971666b01e0
Co-authored-by: Amp <amp@ampcode.com>
|
|
Marks the current tmux session as an agent workload by prepending 'A-'
to its name; pressing the same key again strips the prefix. Fits the
existing convention used by tmux::attach in fish/conf.d/tmux.fish.
Amp-Thread-ID: https://ampcode.com/threads/T-019e7cd6-bcb9-71b8-b21a-da8e7a37dc1d
Co-authored-by: Amp <amp@ampcode.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Remove unused gitsyncer host entry for paul@t450:git
- Remove 'playground' from repository list
- Enhance umount logic to handle already-unmounted NFS mounts gracefully
|
|
|
|
Tag names in the ask CLI do not support hyphens (-). Added a clear
note in both the rules section and the Conventions section of
1-create-task.md so agents use camelCase or concatenated words instead.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
Before shutting down f3s Beelink hosts (f0/f1/f2/f3), attempt to
umount all NFS filesystems currently mounted on earth. NFS mounts on
earth go through stunnel (127.0.0.1:2323 -> 192.168.1.138:2323 CARP
VIP on f0/f1). If any mount is active and cannot be umounted, the
shutdown is aborted to prevent data loss or a hung filesystem.
- Add umount_nfs_mounts() that reads /proc/mounts for nfs/nfs4 types,
attempts to umount each, and returns 1 if any fail
- Call umount_nfs_mounts before proceeding in shutdown, shutdown-f3,
and shutdown-all cases (shutdown-pis skipped: Pis do not serve NFS)
- Update all comments to explain the NFS-over-stunnel architecture and
the safety rationale
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
|
|
|
|
creating-cd-mixes scripts
|
|
|
|
|
|
|
|
|
|
|
|
Installs harper-ls (cargo install harper-ls --locked) and enables it
for markdown and git-commit filetypes where vale-ls is active. Uses
British dialect and hint severity to keep diagnostics unobtrusive.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
f0 sits at the bottom of the rack with a fan directly underneath,
so it consistently runs 10-15°C cooler than f1/f2 at the same load.
f1/f2 are higher up in warmer rising air with no dedicated airflow.
Do not use f0 as a baseline when comparing temps across hosts.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
Replace conservative guesses with actual data from Beelink S12 Pro
reviews and Intel N100 specs (TJmax 105°C, hardware throttle ~100°C).
Add a table with scenario/expected/action rows covering idle through
thermal throttle, plus real-world observations from 2026-05-17 across
all four f-hosts. Adjust remediation steps to match the revised
thresholds (investigate >80°C at moderate load; stop I/O at >90°C).
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
attribution
storage.md (942), k3s-setup.md (342), observability.md (273) split into
per-topic sub-files under references/<topic>/ with short index files at
the original paths.
Drops the SSD TRIM Configuration section added in 8d94f79 and reframes
the Thermal Troubleshooting cascade: the 2026-05-16 f0 incident was
thermal alone, not the multi-cause cascade (autotrim, zrepl interval,
encryption) the previous commit implied. Mitigations applied during
diagnosis are not what fixed it.
Other yesterday additions (zrepl DL-state recovery, CARP-when-ZFS-
suspended, ZFS SUSPENDED runbook, nfs-mount-monitor improvements) are
kept and routed to their respective sub-files.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
|
- observability.md: reflect current state — Grafana/Loki/Tempo disabled
(SQLite-on-NFS unreliable), Alloy running with minimal config only,
Prometheus TSDB wiped and restarted clean (2026-05-16 incident).
Add TSDB recovery runbook. Document .disabled manifest pattern.
- freebsd-setup.md: add coretemp kernel module section — all f-hosts
now have coretemp_load="YES" in /boot/loader.conf for persistent
per-core die temps (hw.acpi.thermal.tz0 is unreliable).
- hardware.md: add f3 IP (192.168.1.133) to LAN table.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
Documents the 2026-05-16 f0 cascade failure (thermal throttling + autotrim=off
+ aggressive zrepl interval → stuck TRIM, multi-second txg syncs, D-state rsync).
Covers symptoms, per-core temp checks via coretemp vs unreliable hw.acpi.thermal.tz0,
Beelink S12 Pro thermal specifics, and step-by-step remediation.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
|
|
|
|
|
|
Switch r0/r1/r2 NFS client mount options from soft,timeo=10,retrans=2,intr
to hard,timeo=600,retrans=3. Removes the soft mount that was causing EIO on
transient stunnel/CARP hiccups; hard mounts retry indefinitely, which is
safer for DB-like workloads (immich, miniflux, audiobookshelf). The intr
option was a no-op since kernel 2.6.25 and is dropped. Navidrome's /data
is now on local-path so it is unaffected by this change.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
Update 'Pods stuck' troubleshooting entry: the script is now driven by
a systemd timer (10 s) rather than a cron job (1 min). Add a new
'NFS Auto-Repair: nfs-mount-monitor' section documenting the repo
layout (f3s/r-nodes/nfs-mount-monitor/), the Rex deploy command, what
the script does, and timer configuration.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
