Conversation
github-actions
Bot
added
vouch:trusted
cursor
Bot
force-pushed
the
cursor/antigravity-mei-orphan-sweep-9d0e
branch
2 times, most recently
from
September 25, 2026 06:22
65efebc to
52b89d3
Compare
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…nup (pingdotgg#14553) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Pre-pingdotgg#12008 health probes unpacked agy_acp_server.exe into %TEMP%\_MEI* and were killed before PyInstaller cleaned up. Profile isolation stopped new leaks but never deleted those leftovers. On Windows driver start, sweep host TEMP/TMP once: delete only _MEI* directories that have Antigravity markers, are older than two days, and are not locked. Unmarked dirs, dirs at or under the two-day cutoff, and locked dirs are left alone.
A marked extract older than two days was deleted as soon as the sweep started. On Windows that recursive remove unlinks unlocked data files before a locked executable returns EBUSY, so a long-running Antigravity process could lose its unpack. The sweep now skips a directory when a live process still has it as _MEIPASS, its cwd, or an open file. On Windows, renaming the directory aside is the open-handle check, and a failed rename leaves every file in place. Verification: from the repo root, vp test run apps/server/src/provider/acp/AntigravitySessionFiles.test.ts apps/server/src/provider/Drivers/AntigravityDriver.test.ts Result: Test Files 2 passed (2), Tests 19 passed (19). The new test holds payload.bin open in a stale marked extract and checks the unopened sibling and nested files stay byte-for-byte intact while an unreferenced orphan is removed. vp run typecheck (apps/server) exited 0. Checked on Linux x64 with Node 24.13.1. Not run against a Windows %TEMP% directory or a real agy_acp_server.exe. Co-authored-by: maco <macodev00@users.noreply.github.com>
cursor
Bot
force-pushed
the
cursor/antigravity-mei-orphan-sweep-9d0e
branch
from
October 1, 2026 08:47
027e7b2 to
d500a00
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed
On Windows, Antigravity driver start now does a one-shot sweep of host
TEMP/TMPfor leftover PyInstaller_MEI*directories created by pre-pingdotgg#12008 health probes.A directory is deleted only when all of these hold:
_MEIagy_acp_licenses.txt,localharness, orgoogle3/third_party/jetski_prod/localharness)EBUSY/EPERMare ignored)Unmarked
_MEI*dirs, young marked dirs, andgoogle3alone are left alone. The real system temp is never listed in tests; the directory is injected.Profile-owned runtime temp cleanup from pingdotgg#12008 is unchanged. The health probe still does not spawn.
Why
pingdotgg#12008 stopped the probe from spawning and isolated new session extracts under the profile. Anyone who already had tens of GB of
%TEMP%\_MEI*leftovers kept them forever. This reclaim is the remaining work from pingdotgg#12239.This is a small reliability fix only. No feature work, no docs, no
.github/pr-assets/.UI Changes
Not applicable.
Checklist