Mercurial & Windows Server 2003

I just set 开发者_开发知识库up Mercurial on our main webserver, hosting repositories via hgwebdir.cgi. The problem I'm having now is when I run hg push from my local machine to the server's repository, it takes an absolutely ridiculous amount of time to push a very small directory, with only a single changeset. Is it possible that I've set something up wrong? I keep getting HTTP Error 502: Bad Gateway.

Looks a bit like issue 2716 which suggests:

Here's a workaround for the problem you are having, basically instead of doing one huge push, you break it down into many smaller pushes:

1. Find out the number of revisions of your repository.

2. Copy and paste the following script, (in bash, use your favorite scripting language if you don't like bash):

   #!/bin/bash
   
   for rev in {1..NUM_OF_REVS}
   do
     hg push -r $rev REPO_URL
   done
   

3. Wait for that to run.

4. If some of the pushes fail, don't worry, the following push will catch things up.

That being said, issues on Windows IIS has been reported as well.

This "blog post comment" also details:

• I got the same error "Bad Gateway" and solved it. Think it's about:

  1. Install Mercurial 1.2.1 on the server. The version that comes with TortoiseHg is not sufficient, it will not drive the CGI application.

• I get a "Bad Gateway" exception when trying to run hgwebdir.cgi from a web application which exists on a different drive to my main system drive.

• If you're using Mercurial 1.5 make sure you are using Python version 2.6.4 to run the cgi scripts in IIS.