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
Move git config/remote to gitrepo package and add global lock to resolve possible conflict when updating repository git config file (#35151)
Partiallyfix#32018 `git config` and `git remote` write operations create a temporary filenamed `config.lock`. Since these operations are not atomic, they mustnot be run in parallel. If two requests attempt to modify the samerepository concurrently—such as during a compare operation—one may faildue to the presence of an existing `config.lock` file.In cases where `config.lock` is left behind due to an unexpected programexit, a global lock mechanism could allow us to safely remove the stalelock file when a related error is detected. While this behavior is notyet implemented in this PR, it is planned for a future enhancement.---------Signed-off-by: wxiaoguang <wxiaoguang@gmail.com>Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
// avoid: ambiguous argument 'refs/a...refs/b': unknown revision or path not in the working tree. Use '--': 'git <command> [<revision>...] -- [<file>...]'
// We have a common base - therefore we know that ... should work
94
-
if!fileOnly {
95
-
// avoid: ambiguous argument 'refs/a...refs/b': unknown revision or path not in the working tree. Use '--': 'git <command> [<revision>...] -- [<file>...]'