"Something went wrong" when creating commit by uploading the file

[Artur Gordashnikov]

I'm updating the file using the following endpoint

/2.0/repositories/{accountName}/{repoName}/src

The same exact code works great with 3/4 repositories, but one returns 500 with the following message

{"type":"error","error":{"message":"Something went wrong","id":"b269a691d3b14d5e85b3316c934d4ef4"}

 I can see the file was updated despite the error.

[Syahrul]

Hey @Artur Gordashnikov 

G'day.

The error code you've shared translated to a timeout error which generally happens if the upload files are large or if there's a network issue while uploading the files.

Though the files were updated in UI, they may partially be uploaded in some cases. 

That said, I would suggest reviewing the files to verify if it does upload everything for standard code files. If it's binaries files, you may need to clone the repository to test them.

I hope this helps.

Cheers,
Syahrul

[Artur Gordashnikov]

Hey @Syahrul thanks for the reply.

The file is a pretty small XML file, only 16KB. It also happens only in this particular repository. Other repositories respond with no errors and I'm uploading this file to 3 repos simultaneously. It sounds like a BitBucket issue rather than a file or network problem.

[Syahrul]

Hey @Artur Gordashnikov 

Noted. Can you consistently reproduce the issue on this specific repository?

If yes, can you see if you can create a commit manually on this repository via the UI//terminal?

This should help identify the behavior if it's an API-only issue or a git terminal.

Let me know the results.

Cheers,
Syahrul

[Artur Gordashnikov]

Hey, @Syahrul sorry for the late reply.

The issue reproduced 9 out of 10 times. The same result was when using the UI. When using the terminal the `git push` almost always succeeds but takes a relatively long time, nearly one minute.

[Artur Gordashnikov]

After a few additional failures to create the commit with the API, my colleague gets an error when trying to `git push`

remote: error: cannot lock ref 'refs/heads/{BRANCH}': Unable to create '/opt/micros/data/cvs/vp0530/data/d-825/r-19070825/./refs/heads/{BRANCH}.lock': File exists.

[Syahrul]

Hey @Artur Gordashnikov 

Thanks for the update.

I have raised a support ticket for you to continue the investigation.

You can check your ticket at the Support portal. 

Cheers,
Syahrul