Closed vgutkovsk closed 3 months ago
os.symlink and ln call the same syscalls. I doubt very much that this is the issue.
Could it be a case of something which has a CWD in the old worktree maybe?
Can you help. Me boil down a repro case?
Thanks @thockin for the suggestion, there was actually something in the synced directory with CWD, it was not very obvious so took me some time to find it. Closing the issue.
When running a script that occasionally executes other scripts synchronized via
git-sync
, there's an issue withPYTHONPATH
resolution in the latest version (4.0.0). Despite updating the symbolic link properly, the main script keeps triggering old files from the previous worktree. This problem doesn't occur withgit-sync
version 3.6.9, suggesting a potential regression. A comparison between the code for symbolic link creation reveals a change in mechanism:git-sync
4.0.0 now usesos.Symlink
instead of theln
command. Although the symbolic links created by both versions appear identical, the issue persists. Assistance in debugging this matter would be greatly appreciated.