You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fsmonitor: Handle differences between Windows named pipe functions
CreateNamedPipeW is perfectly happy accepting pipe names with embedded
escape charcters (e.g. \b), WaitNamedPipeW is not and incorrectly returns
ERROR_FILE_NOT_FOUND when clearly a named pipe with the given name
exists.
For example, this path is problemmatic:
\\batfs-sb29-cifs\vmgr\sbs29\my_git_repo
In order to work around this issue, rather than using the path to the
worktree directly as the name of the pipe, instead use the hash of the
worktree path.
0 commit comments