mirror of https://github.com/go-gitea/gitea.git
d2e994db2c
Partially fix #32018 `git config` and `git remote` write operations create a temporary file named `config.lock`. Since these operations are not atomic, they must not be run in parallel. If two requests attempt to modify the same repository concurrently—such as during a compare operation—one may fail due to the presence of an existing `config.lock` file. In cases where `config.lock` is left behind due to an unexpected program exit, a global lock mechanism could allow us to safely remove the stale lock file when a related error is detected. While this behavior is not yet 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> |
||
|---|---|---|
| .. | ||
| actions.go | ||
| authorizedkeys.go | ||
| breaking.go | ||
| checkOldArchives.go | ||
| dbconsistency.go | ||
| dbconsistency_test.go | ||
| dbversion.go | ||
| doctor.go | ||
| fix8312.go | ||
| fix16961.go | ||
| fix16961_test.go | ||
| heads.go | ||
| lfs.go | ||
| main_test.go | ||
| mergebase.go | ||
| misc.go | ||
| paths.go | ||
| repository.go | ||
| storage.go | ||
| usertype.go | ||