Git import: a tree Orphan at VS Code 9ab2056393c8 (one commit) issue #88
closed: completed andymccall opened this · 0 comments
andymccall
The first 31 000 commits of VS Code imported fresh on the current build (2026-10-09) verify with exactly one difference: at 9ab2056393c8 (2018-02-19, 'notifications - remove old message service and adopt new one', one parent; deletes 5 files, modifies 114, empties src/vs/platform/message/common and src/vs/workbench/services/message/{browser,browser/media,electron-browser}) the imported state is conflicted: Orphan { node acc78159, parent ec78ada2 }, a live node under a parent that is not live. The next commit is clean. Same node ids as the 2026-10-05 import, so deterministic. A small reproduction (nested folders emptied in one commit) does not trigger it. Reproduce with OXY_IMPORT_STOP_AFTER=29720 on ~claude/bench/vscode.git, then find the node's path. Blocks a clean VS Code re-import (issue #81).
The first 31 000 commits of VS Code imported fresh on the current build (2026-10-09) verify with exactly one difference: at 9ab2056393c8 (2018-02-19, 'notifications - remove old message service and adopt new one', one parent; deletes 5 files, modifies 114, empties src/vs/platform/message/common and src/vs/workbench/services/message/{browser,browser/media,electron-browser}) the imported state is conflicted: Orphan { node acc78159, parent ec78ada2 }, a live node under a parent that is not live. The next commit is clean. Same node ids as the 2026-10-05 import, so deterministic. A small reproduction (nested folders emptied in one commit) does not trigger it. Reproduce with OXY_IMPORT_STOP_AFTER=29720 on ~claude/bench/vscode.git, then find the node's path. Blocks a clean VS Code re-import (issue #81).