Corrupted repository, possible solutions?

[Eric Gagnon]

Hello,

I  think I have a corrupted repository on Bitbucket Cloud, when i save I get a "We had trouble committing your changes." message and when I try to merge pull request I get no error, just a spinning wheel, but there are javascript error in Chrome log which suggest bad refs :

{"type": "error", "error": {"message": "Command '['git', 'update-ref', 'refs/heads/master', 'c9008fda1a32728fb897b51356ab1e3004794939', '40e34c7299f866a8ff7d18f9e9e053eb2d3e8d44']' returned non-zero exit status 128", "id": "f5577e472318444c8ce6c03ef12a726b"}}

I tried to fork the project and then transfer the ownership back but the project keep the forking history (to the still corrupted repo), so I don't think it's ideal.

I have opened a ticket yesterday but I'm not sure if there will be a quick followup as I have a free account, is there anything I could try or on my own (while keeping history and all).

Thanks for any help,

Eric

[Eric Gagnon · Accepted solution]

I got an answer from support and after a few exchanges, the issue was identified and solved.

I should have seen that before, the error I was getting from the ui was less informative than the error from sourcetree: 

remote: error: cannot lock ref 'refs/heads/master': Unable to create '/data/c01/n08/p/vp0654/data/d-856/r-28601856/refs/heads/master.lock': File exists.

Once that was found, it was solved quickly but it also confirms that there wasnt much I could do on my side.

Lock deleted.

[Alexei Ferreira]

Hello, could you tell me how did you solve it?

[Eric Gagnon]

"Once that was found, it was solved quickly but it also confirms that there wasn't much I could do on my side."

The best would probably to open a ticket.

Eric

[N-Y Corp]

need help on it please