-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Action (accept_transfer): The process cannot access the file because it is being used by another process. #17885
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is almost certainly a Windows-only issue where some other process might "lock" the file by keeping a handle open. You can try using https://docs.microsoft.com/en-us/sysinternals/downloads/handle to find out which process it is. |
@silverwind handle D:\Gitea |
Yup almost certainly we've locked the repo ourselves. Probably it's in ctx.Repo.GitRepo and we need to close that before we move the repo. |
Repository Transfer requires that the repository directory is renamed - which is not possible on Windows if the git repository is open. Fix go-gitea#17885 Signed-off-by: Andrew Thornton <[email protected]>
Repository Transfer requires that the repository directory is renamed - which is not possible on Windows if the git repository is open. Fix #17885 Signed-off-by: Andrew Thornton <[email protected]> Co-authored-by: Lunny Xiao <[email protected]>
Backport go-gitea#18049 Repository Transfer requires that the repository directory is renamed - which is not possible on Windows if the git repository is open. Fix go-gitea#17885 Signed-off-by: Andrew Thornton <[email protected]> Co-authored-by: Lunny Xiao <[email protected]>
Backport #18049 Repository Transfer requires that the repository directory is renamed - which is not possible on Windows if the git repository is open. Fix #17885 Signed-off-by: Andrew Thornton <[email protected]>
Repository Transfer requires that the repository directory is renamed - which is not possible on Windows if the git repository is open. Fix go-gitea#17885 Signed-off-by: Andrew Thornton <[email protected]> Co-authored-by: Lunny Xiao <[email protected]>
Gitea Version
1.15.6
Git Version
2.34.1
Operating System
Windows Server 2019
How are you running Gitea?
I'm running Gitea as a Windows Service on Windows Server 2019 using LocalSystem identity.
Database
PostgreSQL
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
https://gist.github.com/doggy8088/24746886bc6f55ff933dfef676b8c215
Description
I want to transfer repo's ownership to another account in my On-Prem Gitea installation. After I applied transfer to another account, the account opened his own notification message. Then press the green Approved button. The screen shows 500. All the detailed error log has been attached on this issue.
I doubted it's a bug on Windows Gitea.
Screenshots
N/A
The text was updated successfully, but these errors were encountered: