abort: stream ended unexpectedly when cloning repo

Matt Mackall mpm at selenic.com
Wed Aug 10 19:05:23 UTC 2016


On Wed, 2016-08-10 at 09:49 +0100, Simon King wrote:
> I don't know what all the fields in those logs represent, but if the
> 10th field is the size of the response, then 4294967457 is 161 bytes
> bigger than 4GB, which sounds very suspicious - perhaps you are
> hitting a size limit somewhere?

That seems very likely. In particular, the IIS SSL implementation is known to
have trouble with large streams.

Seriously, you will save yourself a lot of pain if you use any web server other
than IIS. I'd rate hgweb deployment choices something like this:

Linux + Apache: most documented, most reliable, scales well
Linux + Nginx: works ok, minor config gotchas, no real advantages
Windows + Apache: works, reliable, but slower and doesn't scale as well
Windows + hg serve: basically a toy, but at least it's reliable
Windows + IIS: still doesn't scale well, mystery bugs, useless diagnostics

-- 
Mathematics is the supreme nostalgia of our time.




More information about the Mercurial mailing list