Rename (object path): Access is denied when trying to stage files about go-git HOT 9 CLOSED

It seems this has been reported before: src-d/go-git#1155

And was mentioned in some tests src-d/go-git#906

I will do some digging and see if I can figure out the exact cause. The test suite passes fine on my machine (aside from one unrelated failure, which I've fixed) so it seems this issue isn't covered.

from go-git.

I have same issue and tried to figured out what wrong, but my knowledges not enough. I had find only call stack, maybe it will help.

Windows 10
git version 2.26.0.windows.1
go version go1.14.2 windows/amd64

from go-git.

The same occurred to me when I was trying to commit the staged changes

rename C:\Users\test\Desktop\git_repo\.git\objects\pack\tmp_obj_868086824 C:\Users\test\Desktop\git_repo\.git\objects\b1\4c334b1b9aafc09e7d89a73a8d3f6a226eb57f: Access is denied.

In Linux and MacOS, this works fine and the issue seems to occur only on windows

from go-git.

I'm also running into this issue.

from go-git.

I'm having the same issue. Works fine when I'm adding and commiting files manually using cmd/git bash, but not from go-git.

rename E:\linux-server-deployment\.git\objects\pack\tmp_obj_1108885254 E:\linux-server-deployment\.git\objects\1f\518e5980f27b13107cf3f86a82feee0059ddea

It seems that the target object already exists at the disk, so it is unable to rename the tmp to the target one.

from go-git.

Well, has this problem been solved?

from go-git.

I also ran into this problem. Since it is a windows system, I checked the permissions of the .git directory, and it can be run after canceling the read-only permissions

from go-git.

To help us keep things tidy and focus on the active tasks, we've introduced a stale bot to spot issues/PRs that haven't had any activity in a while.

This particular issue hasn't had any updates or activity in the past 90 days, so it's been labeled as 'stale'. If it remains inactive for the next 30 days, it'll be automatically closed.

We understand everyone's busy, but if this issue is still important to you, please feel free to add a comment or make an update to keep it active.

Thanks for your understanding and cooperation!

from go-git.

To help us keep things tidy and focus on the active tasks, we've introduced a stale bot to spot issues/PRs that haven't had any activity in a while.

This particular issue hasn't had any updates or activity in the past 90 days, so it's been labeled as 'stale'. If it remains inactive for the next 30 days, it'll be automatically closed.

We understand everyone's busy, but if this issue is still important to you, please feel free to add a comment or make an update to keep it active.

Thanks for your understanding and cooperation!

from go-git.