What causes git to fail to not work suddenly when "The user held the relationship lock for too long"?

Question

I went back to some code that was open after a few hours, and made some changes to the code, and then clicked it. Suddenly I get this error:

sura@raitorial:~/workspace/conse (master) $ git push Counting objects: 15, done. Delta compression using up to 8 threads. Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 492 bytes | 0 bytes/s, done. Total 6 (delta 5), reused 0 (delta 0) remote: canceling statement due to conflict with recovery remote: LINE 1: ...er"."date_joined" FROM "bb_repository" INNER JOIN "auth_user... remote: ^ remote: DETAIL: User was holding a relation lock for too long. remote: To [e-mail]:sureumar__/conse.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to '[e-mail]:sureumar__/conse.git' sura@raitorial:~/workspace/conse (master) $ 

How can I diagnose the cause of this error?

Answer 1

As the message shows, this is a problem with the end of Bitbucket. You can check the status of your services by visiting http://status.bitbucket.org/ , which will tell you (for example):

Verification We are gradually restoring the contents of incoming messages to mitigate any other replication problems. Any messages you expect to see should appear slowly, as we gradually increase our scheduled maintenance.
June 16, 03:22 UTC

Update . Servicing in the primary database caused an excessive lag behind the replicas used to authenticate Git and Mercurial HTTPS operations. We did not manage the backup and restored the service. Contact our support team if you are still having problems with your taps or pulls.
Jun 16, 02:48 UTC

In progress . We see unforeseen complications in gitweb and hgweb traffic that we are currently solving. Please see this page for updates.
June 16, 02:03 UTC

If there are no current problems in the list, contact support .