mercurial cloning from git bash

[Mads Kiilerich]

Hi

It seems odd that the problem should be caused by the upgrade.

Celery is not involved when cloning, so that doesn't make any difference.

If the problem only was seen with http, then I would blame the proxy. 
Both the problems with ssh rules that out.

Especially for ssh, Kallithea gets out of the way once the connection 
has been established and authenticated. It thus seems like the problem 
is somewhere in the general system. Somewhere that can impact both 
connections to the http stack and to the ssh server.

My best guess would be some kind of network problem, perhaps a timeout 
in a firewall or NAT router. (As the error message suggest.)

As a data point, you could try making the same clone commands from 
another account on the server machine or a machine next to it. (But it 
will probably also be faster that way, so if it works, you can't know if 
you bypassed the location of the problem, or if you just were fast 
enough to avoid hitting the problem...)

If you have a real ssh account on the server machine and can read the 
repos from it, then you can also try to clone from 
ssh://username@IP//srv/repos/reponame without using Kallithea at all.

You can also try with another more recent Mercurial version on the 
client side, perhaps on another machine.

/Mads



On 19/07/2023 11:01, Ed Wong wrote:
> Hi,
>
> I finally was able to upgrade an old Kallithea setup to the
> latest version and migrated the old repositories to the
> new system.  That said, I haven't setup Celery as
> that requires either RabbitMQ or redis.
>
> However, I'm having some difficulties in cloning off
> a mercurial repository (based on Mozilla's mozilla-central).
>
> I tried the following:
>
> 1)
>     hg clone --debug ssh://<ip>/<repo> newrepo
>
>   At this point, it would spew out a long list of
> entries such as "add changeset <cset>"; but would
> hang at some changeset and would just display
> "ad"
>
> 2) hg clone --debug http://<ip>/<repo> newrepo
>
>    Does the same thing as #1, but at one point it
> dumps the following:
>
> .
> .
> add changeset 5f2a7ad96962
> bundle2-input-part: total payload size 85113701
> transaction abort!
> rollback completed
> (sent 3 HTTP requests and 1287 bytes; received 19595741 bytes in response)
> abort: HTTP request error (incomplete response)
> (this may be an intermittent network failure; if the error persists,
> consider contacting the network or server operator)
>
> The mercurial client that comes with git bash (2.40.1)
> is 5.0.2.
>
> Might anyone have any idea how to fix this issue?
>
> Thanks
>
> Ed
> _______________________________________________
> kallithea-general mailing list
> kallithea-general at sfconservancy.org
> https://lists.sfconservancy.org/mailman/listinfo/kallithea-general