Occasional http 500 (KeyError) errors on clone/pull/push

[Bruce Cran]

On 12/2/2013 1:48 PM, Bruce Cran wrote:
 > Since no changes were found, they should have been skipped - but for 
some reason it aborts instead.

This sounds like http://bz.selenic.com/show_bug.cgi?id=3781 (fixed in 2.5):

"It is possible to reference read-only repository as subrepo. Push in a 
super repo recursively push subrepo. Those pushes to potential read only 
repo are not optional, they are "suffered" not "choosed". This does not 
break because as the repo is untouched the push is supposed to be empty. 
If the reference repo locally contains draft changesets, a courtesy push 
is triggered to turn them public. As the repo is read only, the push 
fails (after possible prompt asking for credential). Failure of the 
sub-push aborts the whole subrepo push."

-- 
Bruce