Closed otac0n closed 11 years ago
In at least one case, this was caused by file permissions. The refs/heads/master file was owned by "Administrators" instead of "NETWORK SERVICE". How it got that way is unclear, but it could be due to a backup/restore issue.
If this is the case, the error should be logged on the server and, if possible, on the client.
I have not seen this happen anywhere since I opened the issue. Based on this, I am going to conclude that there was a process on the machine that was interfering. While the error reporting is not ideal, the issue can be closed, since nobody else is experiencing the same behavior.
I don't have a good repro case yet, but every once in a while, the remote repository fails to update a ref to point to the pushed commit.
It accepts the commits just find, and pushing the commits to a new branch also succeds. But even after that, the old branch will not update.