Issue #2530 resolved

Push to Large Kicks the Bucket when stripping

Aldrin Leal
created an issue

When I ask for stripping on filmow/r0, it gives me an error message

Please strip for me if needed. Thank you

Comments (10)

  1. Erik van Zijst staff

    Hi Aldrin,

    You are running into a server-side timeout because the strip takes too long. I had a quick look at the repo and it appears to be a pretty large repo containing only a single changeset. Also, there is a very large, 882MB binary database dump file in it, which causes the strip to take longer than 30s.

    The best thing to do is to run the strip locally and then push to Bitbucket.

    Cheers, Erik

  2. Erik van Zijst staff

    Nevermind, you won't be able to push the stripped repo..

    Instead, I'm running the strip for you, directly on the server. You should have an empty repo again in a bit.

    N.B. You might want to limit the use of exceptionally big binary files in your repository.

    Cheers, Erik

  3. Aldrin Leal reporter

    Erik,

    Thats exactly what I needed - remotely stripping and redoing the whole repo.

    I know I commited a very large file (there wasn't any SCM previously) - thus the reason for stripping, and I missed a few globs on my .hgignore.

    Thank you.

  4. Aldrin Leal reporter
    • changed status to open

    Could you just take a look at the server-side logs? It seems something is still left (probably some permissions, I think):

    C:\projetos\sources\filmow>hg push https://aldrinleal@hg.modafocas.org/filmow
    http authorization required
    realm: Bitbucket.org HTTP
    user: aldrinleal
    password:
    pushing to https://aldrinleal@hg.modafocas.org/filmow
    searching for changes
    abort: HTTP Error 500: Internal Server Error
    
  5. Log in to comment