4 Commits

Include renames

Author	SHA1	Message	Date
retoorandClaude Sonnet 5	7880bf4b31	Fix container sync races that leaked orphan blobs; add a system-prune CLI command ... sync_workspace (user-triggered) and the reconciler's sync_bidirectional_sync could run concurrently for the same project, and store_upload's read-then- write on a changed path meant two racing imports each wrote their own blob while only one ever got referenced - the loser leaked forever. Combined with no build-artifact exclusion, an actively-compiling workspace hit this constantly and leaked 5.9M orphan blobs (~96GB) in production before it was caught. Closes it at the root: api._sync_dir_bidirectional_locked serializes both call sites per-project (non-blocking - a project already mid-sync is simply skipped until the next tick), and IMPORT_SKIP_NAMES/IMPORT_SKIP_EXTENSIONS keep build output (build/, dist/, *.o, *.pyc, ...) out of the walk entirely. Recovering what already leaked is a separate concern: a new CLI subcommand (plus matching make targets) sweeps soft-deleted attachment/project-file blobs and any blob with zero DB reference at all, plus orphaned container workspace directories. run_maintenance_cleanup.sh wraps the existing prune/clear commands for routine disk upkeep. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BWJy6PrMMt5hwWxQwia2rd	2026-09-08 03:43:49 +02:00
retoorandClaude Sonnet 5	70ceb3cf81	Make workspace/project file sync propagate deletions instead of resurrecting them ... The old sync compared only the two live sides (project rows vs workspace files), so a file present in the project but missing on disk was indistinguishable from "never materialized here yet" - it always got re-exported, which is why deleting a file inside a container made it come back. The mirror direction had the same bug: a file deleted from the project's file editor was silently re-imported from the container's stale copy on the next tick. Fixes it with a persisted per-file sync baseline (new project_file_sync_state table: db_epoch/fs_epoch as they stood right after the previous sync), the same role a rsync/Unison state file plays in any real bidirectional sync. Deleting on either side now propagates to the other, unless the deleted side's counterpart was edited after the last sync, in which case the edit wins and the file is restored. A read-only project always exports (never imports, including on tie) and always removes a workspace's stale local copy, so it stays a faithful mirror. Sync of an unchanged file is now a true no-op (zero writes) instead of rewriting it every ~60s tick forever. sync_dir_bidirectional's return dict gains deleted_in_project/ deleted_in_workspace alongside exported/imported; both API call sites already pass the whole dict through untouched. The instance sync toast now summarizes all four counts instead of just imports. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TjdKTWgWpW2SMNW8SFqxz5	2026-09-03 08:47:57 +02:00
retoor	6514261730	Route container proxies through the leg that is actually reachable ... The workspace editor hung for 60s and then 504'd. Three independent faults were stacked behind that one symptom. Reachability: editor_target delegated to proxy_target, which returns CONTAINER_PROXY_HOST plus the published host port and never falls back to the container. From inside the app container that address crosses docker0 into the host INPUT chain, whose policy is DROP with an allow-list that does not include the published port range, so the packet was dropped and the request hung rather than being refused. Measured from the app container: container_ip:8443 answers 302, gateway:20006 is dropped. One shared reachable_target now prefers the direct container leg and falls back to the published port, and editor_target uses tunnel_target as services/containers/CLAUDE.md already required. The same defect affected /p/{slug} ingress and every tunnel, since all three resolved through proxy_target. The recorded measurement that motivated the old order (container_ip times out, gateway connects) no longer holds: make docker-attach puts the app on the instances' bridge network, which is what makes the direct leg work. Duplicate response headers: the forwarding core relayed the upstream Date and Server alongside the ones the serving layer generates, so every proxied response carried two of each. Both are singleton headers and duplicating them is malformed HTTP. Serialization: WorkspaceViewOut declared flag_reason and three sibling strings as str, so a NULL column made the workspace page 500 for JSON clients. Documents the two public hostnames and the devplace.net SSH tunnel, so a future session does not conclude the site is down after pointing curl --resolve at an address the hostname does not resolve to, and adds the layered procedure for diagnosing a production failure. Verified on production with Playwright over both hostnames: the code-server login renders and the workbench loads. Suite: 3345 passed.	2026-08-13 12:59:53 +02:00
retoor	6cac64a3f6	Update	2026-08-10 00:23:20 +02:00