mARTin-B78
9d4e40e4e3
Some checks are pending
Playwright Tests / test (push) Waiting to run
The "update on reboot" unit silently did nothing useful. boot-update.sh piped every command into tee, so `set -e` only saw tee's exit status: a failed npm install or build left a half-built tree and still logged "Boot update finished". It also used npm install (rewrites package-lock.json, so the next git pull aborts), had no GIT_TERMINAL_PROMPT=0, and was not wrapped in a function even though git pull rewrites it mid-run. The unit's TimeoutStartSec=300 was the other half: npm ci + prisma generate + next build takes far longer than 5 minutes in the container, so systemd SIGTERMed the oneshot mid-install and left a node_modules tree npm could no longer remove (ENOTEMPTY on rmdir node_modules/date-fns/isEqual). Also resyncs package-lock.json with package.json, missed in the 1.115.0 commit. v1.115.1 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| backup-db.sh | ||
| boot-update.sh | ||
| create-test-user.ts | ||
| deploy.sh | ||
| docker-entrypoint.sh | ||
| generate-vapid-keys.ts | ||
| lxc-setup.sh | ||
| my-weekly-todo-update.service | ||
| push-scheduler.ts | ||
| seed-connection.ts | ||
| supabase-setup.sh | ||
| test-cloudkit-reminders.py | ||
| update-app.sh | ||
| update-server.sh | ||
| verify-schema.ts | ||