Issue #4945 resolved

Accepting a pull-request results in 500 internal server error.

basbloembergen
created an issue

I'm currently trying to accept a pull-request but it always results in a 500 internal server error on this url:

POST: https://bitbucket.org/mediamonks/..reponame../pull-request/6/update-16-10-2012/fulfill Guru meditation: 7d73b71ad2184474983ed2a26081112c$7eeb91517219778bc27c04ec514271f3

I've also tried it with the owning account and different browsers but it doesn't seem to help.

Any information would be appreciated :-)!

Comments (11)

  1. Nicolas Venegas

    Hi Bas

    There was a lock file left behind on your repository in our filesystem that was causing those requests to timeout (as they were waiting for the lock).

    I've cleared it out. Can you try accepting that pull request once more?

    Cheers

    Nicolas

  2. basbloembergen reporter

    (Reply via basb...@gmail.com):

    Hi Nicolas,

    That doesn't seem to have helped, still getting the 500 error!

    Regards, Bas

    On Tue, Oct 16, 2012 at 6:02 PM, Nicolas Venegas <issues-reply@bitbucket.org

    wrote:

  3. Nicolas Venegas

    Hi Bas

    Sorry, I didn't realize that after cleaning up the locks the output of hg verify indicated there was an abandoned transaction found in the repo, and that I should run hg recover.

    I've now run hg recover and it looks like the repo is fine. Would you indulge me once more and try fulfilling that pull request?

    Cheers

    Nicolas

  4. basbloembergen reporter

    (Reply via basb...@gmail.com):

    Hi Nicolas,

    We're making progress :-)! I'm now getting a 502 Bad Gateway!

    Regards, Bas

    On Wed, Oct 17, 2012 at 3:45 AM, Nicolas Venegas <issues-reply@bitbucket.org

    wrote:

  5. basbloembergen reporter

    Hi Nicolas,

    I just deleted both forks and forked them again, repushed my changes and recreated the pull-request but I'm still getting 500 internal server errors.

    Regards, Bas

  6. Nicolas Venegas

    Hi Bas

    For some reason the merge process, when triggered via our website, is taking longer than 30 seconds; at this point, the request is killed, leaving the repository with left behind locks and an abandoned transaction.

    We plan on deploying performance improvements to accepting a pull request soon (including moving the merging part into a background task that can take as long as it needs to, rather than being killed 30 seconds in).

    For the moment, I suggest manually merging the branches in your pull request and pushing up the result to bitbucket.org

    Finally, would you mind opening up a support ticket (by mailing support@bitbucket.org) so that we can discuss some specifics about your repository and try to figure out why it is failing?

    Regards

    Nicolas

  7. basbloembergen reporter

    (Reply via basb...@gmail.com):

    Hi Nicolas,

    I've noticed, thanks alot!

    Regards, Bas

    On Thu, Jan 10, 2013 at 8:02 PM, Nicolas Venegas <issues-reply@bitbucket.org

    wrote:

  8. Log in to comment