1. Summary
  2. Files
  3. Support
  4. Report Spam
  5. Create account
  6. Log in

Ticket #26077 (assigned)

Opened 11 months ago

Last modified 8 months ago

Mercurial issue

Reported by: lenclud Owned by: ctsai
Keywords: Cc:
Private: no

Description

I'm trying to push almost 900MB of files into the Mercurial depot for the following projects https://sourceforge.net/projects/symbian/

Everything goes smoothly for a while until it gives back HTTP Error 500: Internal Server Error. It looks like the error happens shortly after the file upload completes.

Can you help me out with that? Should I split it into multiple smaller push?

Change History

Changed 11 months ago by ctsai

  • keywords PEND added
  • owner set to ctsai
  • status changed from new to assigned

Hmm, it seems that breaking it into smaller chunks would probably help.

Alternatively, your repo is mounted via the Shell service, so you could try uploading a full copy of your repo and shoehorning it in place (it will be mounted at /home/hg/p/symbian/code)

Let me know if that helps!

Regards,
Chris Tsai, SourceForge.net Support

Changed 11 months ago by lenclud

Ok I can use Putty to open a shell. How can I upload the repository then? Sorry I'm not that savvy with nix shells.

Changed 11 months ago by lenclud

So I uploaded a zipped copy of my local clone using SCP. However it seems I don't have the permission to copy it to /home/hg/p/symbian/code.

Changed 11 months ago by ctsai

  • keywords SOG added; PEND removed
  • owner changed from ctsai to burley

Hmm, indeed, I'm seeing the same behavior. While the repo is mounted and readable there, it doesn't appear to be writable. I'm escalating this to our operations team to get the permissions sorted out.

Regards,
Chris Tsai, SourceForge.net Support

Changed 9 months ago by ctsai

  • keywords SCM P3 added

Changed 8 months ago by moorman

  • keywords SOG SCM P3 removed
  • owner changed from burley to ctsai
  • summary changed from Push ends with HTTP Error 500: Internal Server Error to Mercurial issue
Note: See TracTickets for help on using tickets.