The sound distributed version control system

#485 Clone via ssh hangs

Closed on July 21, 2021
hoogs on July 21, 2021

It was working perfectly fine via ssh when both client and server used pijul version alpha.48 (iirc). I just reinstalled both ends with alpha.52 and re-initialised a repo on the server where pijul ls gives 137 items, and when running clone on the client I now get:

> pijul clone my_account@my_server:path_to_repo/my_repo
Downloading changes [==================================================] 1/1
           Applying [==================================================] 1/1

which then just hangs with no obvious network activity. Has this been seen before, or any suggestions for diagnosing?

tankf33der on July 21, 2021

Do you have self hosted pijul ?

hoogs on July 21, 2021

Yes. When I downgrade to pijul alpha.51 (from 52) on both ends, same outcome, only showing 1/1 artefact transfer, and hangs. Can’t downgrade back to 48, errors in compilation.

tankf33der on July 21, 2021

upgrade to latest pijul, try to clone and run iotop at the same time and you should see disk activities.

Give me address in DM I would like to clone too.

tankf33der on July 21, 2021

I have a multi GB repo linux3x. Try to clone it, should be fine.

hoogs on July 21, 2021

Thanks for the interest, unfortunately I don’t have time to mess around with this now. I’ll circle back and try a newer version in the future.

pmeunier added a change on July 21, 2021
LJFJEX43HDS33O5HCRXH7AR3GTQZDHNWHEQBOERDNPNXR3B3XZ3QC
main
pmeunier on July 21, 2021

This was due to the protocol being tested too much on my own implementation of SSH, rather than on OpenSSH. The attached patch fixes it. Thanks for reporting!

pmeunier closed this discussion on July 21, 2021