Skip to content

Fix generation links removed by unrelated pnpm operations - #549

Open
yaojin3616 wants to merge 4 commits into
mainfrom
agent/debugger/b9158ad60d0f
Open

yaojin3616 wants to merge 4 commits into
mainfrom
agent/debugger/b9158ad60d0f

Conversation

@yaojin3616

Copy link
Copy Markdown
Contributor

Summary\n- remove generation-owned entries from the pnpm lockfile importer during projection isolation\n- keep generation paths out of pnpm ownership while retaining the market-facing manifest after the operation\n- cover legacy lockfile entries in the pnpm runner regression test\n\nFixes #464\n\n## Verification\n- npm test -- --run test/pnpm-runner.test.js\n- npm test -- --run test/generation-projection.test.ts\n- npm run typecheck (fails on existing test/session-delete-remote.test.ts TypertRemoteNamespace.delete typings)

@cinderzhan cinderzhan self-assigned this Sep 24, 2026
@yaojin3616

Copy link
Copy Markdown
Contributor Author

Failure-path review: pnpm-runner.mjs:344-350 writes the manifest isolation before reading/writing the lockfile. A lockfile error occurs before a restore callback is returned, so this operation can leave the live projection partially isolated. The persistent marker may allow cold-start recovery; this is not a claim of permanent data loss. Please make preparation/restoration transactional for read/write failures and add real-pnpm plus multi-importer/quoted-key cases. Keeping the requirement open; current target runner has no equivalent fix. No real installation or Windows failure injection was executed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants