Skip to content

DB dispatch: handler: log prune reads whole lines, per this file's own rule The snapshot prune two hundred lines above states it: xargs splits on whitespace, so a path containing a space reaches rm -f as two fragments, the second resolved relative to cd "$GAMEDIR" -- inside the user's PAK library. The log prune still used xargs. Safe today only because $LOGDIR and the generated names happen to contain no spaces, i.e. correct by accident. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> #12

DB dispatch: handler: log prune reads whole lines, per this file's own rule The snapshot prune two hundred lines above states it: xargs splits on whitespace, so a path containing a space reaches rm -f as two fragments, the second resolved relative to cd "$GAMEDIR" -- inside the user's PAK library. The log prune still used xargs. Safe today only because $LOGDIR and the generated names happen to contain no spaces, i.e. correct by accident. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

DB dispatch: handler: log prune reads whole lines, per this file's own rule The snapshot prune two hundred lines above states it: xargs splits on whitespace, so a path containing a space reaches rm -f as two fragments, the second resolved relative to cd "$GAMEDIR" -- inside the user's PAK library. The log prune still used xargs. Safe today only because $LOGDIR and the generated names happen to contain no spaces, i.e. correct by accident. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> #12

Triggered via push August 14, 2026 19:36
Status Success
Total duration 9s
Artifacts

dispatch_db.yml

on: push
dispatch
5s
dispatch
Fit to window
Zoom out
Zoom in