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> |
||
|---|---|---|
| .. | ||
| avatar.go | ||
| collaboration.go | ||
| default_branch.go | ||
| deploy_key.go | ||
| git_hooks.go | ||
| lfs.go | ||
| main_test.go | ||
| protected_branch.go | ||
| protected_tag.go | ||
| public_access.go | ||
| secrets.go | ||
| setting.go | ||
| settings_test.go | ||
| webhook.go | ||