mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-11-16 03:31:44 +01:00
## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work > - Recovery continues a cut-off task automatically. It first lets a previous process that still runs on this host settle, for about ten minutes at most. > - A server test proves that wait. It failed once on master at03309f1650in the "Cloud readiness" run, and the failure blocked the staging release. > - The test stamps the run with `Date.now() - process.uptime()`. The product compares the stamp with the start time that the OS reports, and a gap of 1 s or more means "a different process with a reused PID". > - The OS time is truncated to whole seconds (Linux `btime`, macOS `ps -o lstart`), and Node starts some milliseconds after the fork. Thus the gap is sometimes 1 s or more, and the product correctly continues the task. > - This pull request makes the test stamp the same OS-observed start time that production records. > - The benefit is a deterministic test that still proves the wait and its ten-minute upper bound. ## Linked Issues or Issue Description **What happened?** `server/src/services/fresh-continuation-fallback.test.ts > lets a previous process still running on this host settle first, for about ten minutes at most` failed on master (Cloud readiness run 43776843790, job "verify / General tests (server (2/10))"). Received `{ kind: "continued" }`, expected `{ kind: "exact_recovery_pending", reason: "previous_process_running" }`. **Expected behavior** The test passes on every host. It only fails when the product does not wait for a live previous process. **Steps to reproduce** 1. Run the test about 15–30 times on macOS under CPU load (for example 24 busy loops on 18 cores). 2. About 1 in 13 runs fails with the same assertion as CI. 3. On Linux, the gap is `frac(boot time)` plus Node startup. Thus a runner whose boot time has a fractional second near 1 fails, and other runners pass. **Paperclip version or commit**03309f1650(master). **Additional context** This is not a product regression. Production writes `processStartedAt` from `readProcessStartedAt` (`persistHeartbeatRunProcessMetadata`), which is the same source that the owner proof reads. Thus production compares two equal values. Neither #21831 nor #21835 changed this path. ## What Changed - `fresh-continuation-fallback.test.ts`: `liveIdentity()` now records `observedProcessStartedAt(process.pid)`, the OS-observed start time that a run records. It throws if the host cannot report the time, so the test cannot pass by accident. - `completed-turn-cleanup-hold-settle.test.ts`: the live controller stamp now uses `currentProcessStartedAtMs()`, the value that this server stamps on its own claims. It had the same `Date.now() - process.uptime()` pattern. - No product code changed. No assertion changed or became weaker. The ten-minute upper bound assertion stays. ## Verification - Gap probe (fresh Node processes, `Date.now() - uptime` minus the OS start time): - macOS under load: 2 of 200 processes had a gap of 1 s or more (max 1017 ms). - Linux (`node:24-bookworm-slim`): gap 340–396 ms, of which 337–345 ms is `btime` truncation. This value is fixed for each host boot, so some CI hosts are always near or past 1 s. - `npx vitest run src/services/fresh-continuation-fallback.test.ts -t "previous process still running|recycled PID"`, repeated under CPU load: see the before/after counts in the comment below. - `npx vitest run src/__tests__/completed-turn-cleanup-hold-settle.test.ts`: 10 passed. ## Risks - Low risk. Only two test files changed. - If a CI host cannot read a process start time, the changed tests now throw a clear error. Before this change the product would also return "unprovable" there. ## Model Used - Claude Opus 5.5 (`claude-opus-5-5`), Anthropic, used through Claude Code with tool use (shell, file edits) and extended reasoning. ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [x] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work - [x] I have searched GitHub for duplicate or related PRs and linked them above - [x] I have either (a) linked existing issues with `Fixes: #` / `Closes #` / `Refs #` OR (b) described the issue in-PR following the relevant issue template - [x] I have not referenced internal/instance-local Paperclip issues or links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip` URLs) - [x] My branch name describes the change (e.g. `docs/...`, `fix/...`) and contains no internal Paperclip ticket id or instance-derived details - [x] I have run tests locally and they pass - [x] I have added or updated tests where applicable - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [ ] All Paperclip CI gates are green - [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups - [x] I will address all Greptile and reviewer comments before requesting merge 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>