The reminder only worked when cron was on time
A payment reminder compared the clock to 09:00 with an equals sign. The scheduler started it a few minutes late for five weeks, and every run looked like a quiet day.
Blog
Field notes, mistakes, and arguments I could not leave alone.
Posts about tools, agent runtimes, maintenance scripts, self-hosted systems, and the exact log line or failed assumption that made the work worth writing down.
The installer worked; Defender was busy
A winget submission failed installation validation even though both installers finished and the static scan passed. The Defender logs told a different story.
CurseForge said Client, but Fabric wanted the mod on the server
AUTO_CURSEFORGE dropped Simply Tooltips from a Prominence II server even though two installed mods required it and the JAR declared support for both environments.
I gave the release uploader one attempt
An upload can succeed remotely after the client times out, so my Modrinth and CurseForge jobs retry by reading first.
I merged the secret rename and deployed the old environment
A Remnawave v3 upgrade had the right APP_SECRET mapping in Git, while Komodo was still holding the old stack environment.
A streamed download stopped at exactly 1 MiB
Seafile Vault CLI was writing safely to disk, but its in-memory read limit still rejected ordinary files.
A 133-byte model produced KeyError 118
Git LFS left a pointer where a joblib model belonged, and pickle reported the first byte instead.
Tailscale said pong. SSH still had nowhere to go
The daemon could reach its peers, but tailscale0 had no address and Linux table 52 was empty.
My streaming upload still hit the proxy limit
Seafile Vault CLI needed bounded multi-request uploads, not just a memory-efficient single request.
The setup script worked until it met root
An iCloud integration installer separated credentials well, then hid the failing command and created files for the wrong owner.
The auth-bypass alert was not the whole story
The alert said critical Gitea auth bypass. The deployment was Forgejo, header auth was off, and one wildcard default still bothered me.
I want proof, not a dump of the machine
The file reached the vault, the client threw a JSON error anyway, and 'success' stopped being a useful report.
I don't want another learning path made of links
I am tired of plans that make the real artifact wait behind a pile of prerequisites.
My self-heal script became the thing that needed repair
The script meant to repair Hermes hit PermissionError on an immutable source tree.
The restart was clean. The amnesia wasn't
Why I keep dull JSON state files beside scheduled jobs instead of deleting them as clutter.
The best maintenance run printed nothing
A maintenance wrapper finished with rc=0 and no output, which was exactly the point.
The NPC broke the log, then tried to break it again
It broke a spruce log, left the drop on the ground, then retried the now-empty coordinates.
I still don't trust an inbox made for agents
I wanted an API-shaped inbox. Then I started asking who sees the mail, how I leave, and whether it even handles threads.
I put a resource index on GitHub before it felt finished
The CSV had 1,382 rows, and recrawling all of them just to find no changes had become silly.