# Many errors when cloning pijul\_org/pijul

**URL:** <https://discourse.pijul.org/t/many-errors-when-cloning-pijul-org-pijul/260>\
**Category:** Question\
**Created:** [January 10, 2019, 1:55pm UTC](https://discourse.pijul.org/t/many-errors-when-cloning-pijul-org-pijul/260 "2019-01-10T13:55:20Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![laumann](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/laumann/32/8_2.png) [@laumann](https://discourse.pijul.org/u/laumann)\
**Post date:** [January 10, 2019, 1:55pm UTC](https://discourse.pijul.org/t/many-errors-when-cloning-pijul-org-pijul/260/1 "2019-01-10T13:55:20Z")

</div>

I wanted to get a fresh clone of [pijul\_org/pijul](https://nest.pijul.com/pijul_org/pijul), and eventually succeeded, but was left with the following shell session:

```bash
$ pijul clone https://nest.pijul.com/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.com/pijul_org/pijul/.pijul/patches/6scnHAmkHF3wAnC3UNHcSAsvS4NjXgwunBZq2fbzK5oaxkfuXDzP6NddpRF88zeMF2PyaLM2FXgsdL7N3kRC1r3Z.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
$ cd pijul
$ pijul pull https://nest.pijul.com/pijul_org/pijul --set-remote origin
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.com/pijul_org/pijul/.pijul/patches/6HLHUW8GwKdKAc24RnBDayQcv5DvyeYEg7Q6RcNGSLkRo782sk6MTMGNexHWgYffestFkoLPTq7NN2BQ1TPYUL7c.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
$ pijul pull https://nest.pijul.com/pijul_org/pijul --set-remote origin
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.com/pijul_org/pijul/.pijul/patches/885EePVNrfjZrKozEmf2pYsDyqiFKQ5yLk31rdetHft4VxgE6MGQaqRfJNiG8cEk8LnAx31DGYa6rWSSj6iYRFLp.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
# ... 9 additional panics later, all patches are downloaded ...
$ pijul pull https://nest.pijul.com/pijul_org/pijul --set-remote origin
Pulling patches: 100% (205/205), done.
Hash: 9tNKV1UL5cYbw3gpDScSfoZSRthQ3a6KHHKMQTjA1CyCumqrVcXey6t37qJMHURpZQwZt1UsKoj3bhNPfevwdhTK
Authors: Pierre-Étienne Meunier <pe@pijul.org>
Timestamp: 2018-02-27 14:44:24.130178136 UTC
    Init
Shall I pull this patch? [ynkad?] a
Applying patches: 100% (205/205), done.
There are pending conflicts waiting to be solved:
    libpijul/src/fs_representation.rs
    pijul/src/commands/fs_operation.rs
    pijul/src/commands/status.rs
    pijul/src/commands/record.rs

```

I don’t think this is expected 😄 Am I doing something wrong? I’m thinking the panics are network failures of some kind, but then being launched straight into conflicts surprised me quite a bit.

* * *

This might be related to:

> [@"pijul pull" command not working for the pijul repo](https://discourse.pijul.org/t/pijul-pull-command-not-working-for-the-pijul-repo/154):
>
> This was what I did last night: pijul clone https://nest.pijul.com/pijul\_org/pijul cd pijul/ pijul pull The last command gave the following error: error: Missing remote repository That’s very strange.

(I got the idea of adding `--set-remote origin` from there.)

---

<div class="post-metadata">

**Author:** ![flobec](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/flobec/32/23_2.png) [@flobec](https://discourse.pijul.org/u/flobec)\
**Post date:** [January 15, 2019, 10:50am UTC](https://discourse.pijul.org/t/many-errors-when-cloning-pijul-org-pijul/260/2 "2019-01-15T10:50:18Z")

</div>

> [@laumann](#):
>
> I don’t think this is expected 😄 Am I doing something wrong? I’m thinking the panics are network failures of some kind, but then being launched straight into conflicts surprised me quite a bit.

Yes, the latest patch in the repository causes a bunch of conflicts. You can pull from the “investigate\_conflicts” branch until things are sorted in `master`.

---

<div class="post-metadata">

**Author:** ![flobec](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/flobec/32/23_2.png) [@flobec](https://discourse.pijul.org/u/flobec)\
**Post date:** [January 17, 2019, 6:51pm UTC](https://discourse.pijul.org/t/many-errors-when-cloning-pijul-org-pijul/260/3 "2019-01-17T18:51:19Z")

</div>

This is now fixed, hopefully.

---

<div class="post-metadata">

**Author:** ![qyh](https://avatars.discourse-cdn.com/v4/letter/q/ee59a6/32.png) [@qyh](https://discourse.pijul.org/u/qyh)\
**Post date:** [January 19, 2019, 8:05am UTC](https://discourse.pijul.org/t/many-errors-when-cloning-pijul-org-pijul/260/4 "2019-01-19T08:05:50Z")

</div>

Hi, I’m new to pijul as well and had the same problems trying to clone from source, as of today on the latest version 0.11.1 built from source.

Running `pijul clone` throws an error straight away, and going into the directory and pulling runs fine until `167/207 patches`, where it starts panicking out once every few patches, and finally ended with the same conflicts listed above.

Also strange was the count jumping instantly from 197/207 to completion at the end of the sequence.

Is there any way to check if the data I pulled is complete and not corrupted?

```bash
$ pijul pull https://nest.pijul.org/pijul_org/pijul --set-default
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.org/pijul_org/pijul/.pijul/patches/983XuNNx1WDYXqTtJ9Acbfob3pvbmjpsksJXriq9VJEG1iVQ2nq9zWhuKrZ2oSX89fvwwWsPXEoyom5ivEyda6gE.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
$ pijul pull https://nest.pijul.org/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.org/pijul_org/pijul/.pijul/patches/8tqfDssc1TFLuYxXKz6nd1vtTMx6ggRooV5kT245dRDT5zWgAaTPJexo7gUEaELQ1ShUtqEANDbMBUL59P7qAvGc.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
$ pijul pull https://nest.pijul.org/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.org/pijul_org/pijul/.pijul/patches/7K5THRbXpmLt1QqzLTWQNdYAcz7Yp7oWgoMk6X2T4TgX6SrbKGacPoYG7t83J56pJvQmiGoMqQpczzH5KP4vpHo8.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
$ pijul pull https://nest.pijul.org/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.org/pijul_org/pijul/.pijul/patches/B2kM4BmmNdUFL7U5Ra8W8BVrZom3ryejWY6t1eRHKrt74TqRvSEywDtnexZrQgHf6RMwBq7LV5Gf6NRw9f1WdQcr.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
$ pijul pull https://nest.pijul.org/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.org/pijul_org/pijul/.pijul/patches/6QmTyjgPnKZKaideBffsgpMrexc25tphT9zgDd95MtiV4jpksPicF3Yjq7Mi7kztwGaKANrkbCcU1ptGuoufF1DM.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
$ pijul pull https://nest.pijul.org/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.org/pijul_org/pijul/.pijul/patches/6BPqPsJyXxWMPQAKpuzoGtHrC1gr2QAyhMarbKdb537oRFdJmB4rDqhnqDnYvAb5cTm8AKFaRmj7B1PCDUifwCb3.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
$ pijul pull https://nest.pijul.org/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.org/pijul_org/pijul/.pijul/patches/9pjoFiawccUE94wrGQn9jXiCatKtuZHsoUoDxzoXwyjiWSGVYaReS6TiGBDhdXW3RXm6EXP1shpkqcB9mFYsokgX.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
$ pijul pull https://nest.pijul.org/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.org/pijul_org/pijul/.pijul/patches/7Z4kLYUhXKTTyEzxyBzCZHcghGskqYgcthBQ1FP8EByjES7Zi1womQpQQT8KWGz9kJqJJmQNupC3XZCdEuDnVWdZ.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
$ pijul pull https://nest.pijul.org/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.org/pijul_org/pijul/.pijul/patches/6GHwSTevaRZkJPdr5Jze1d5jikSUUcMrcfwSZtbNJgndKfcQwjrM5BSz4Kr6aRt5nzwgRqfsaYNfJPktPFfpU62d.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
$ pijul pull https://nest.pijul.org/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.org/pijul_org/pijul/.pijul/patches/6RM7Mg5Lagwh1sjfCtHqxkZsBKnPx8TduJ4WGnmfcEytxhnrG3c4AhQs3pGRRcaybvw97BFE1Z3LQhkw3Yta7RDk.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
$ pijul pull https://nest.pijul.org/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Hyper(Error { kind: Incomplete }), url: Some("https://nest.pijul.org/pijul_org/pijul/.pijul/patches/B8GjgZZrvwHTFa7y5RphNDQrKY5979RUaC59GGChAUUG5zdneAKHdVxyVFHAfq8ZRbFKKycGGvBQ2k3yik9YM6Mk.sig") }', libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
$ pijul pull https://nest.pijul.org/pijul_org/pijul
Pulling patches: 100% (207/207), done.

Hash: 9tNKV1UL5cYbw3gpDScSfoZSRthQ3a6KHHKMQTjA1CyCumqrVcXey6t37qJMHURpZQwZt1UsKoj3bhNPfevwdhTK
Authors: Pierre-Étienne Meunier <pe@pijul.org>
Timestamp: 2018-02-27 14:44:24.130178136 UTC

    Init

Shall I pull this patch? [ynkad?] a
Applying patches: 100% (207/207), done.
There are pending conflicts waiting to be solved:
    libpijul/src/fs_representation.rs
    pijul/src/commands/status.rs
    pijul/src/commands/record.rs
    pijul/src/commands/fs_operation.rs

```

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [February 23, 2019, 11:18pm UTC](https://discourse.pijul.org/t/many-errors-when-cloning-pijul-org-pijul/260/5 "2019-02-23T23:18:32Z")

</div>

THIS IS FIXED! I’M SO HAPPY!

I’ve been trying to fix this for almost two months now, tried everything I could. I’m sorry for the inconvenience.

---

<div class="post-metadata">

**Author:** ![laumann](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/laumann/32/8_2.png) [@laumann](https://discourse.pijul.org/u/laumann)\
**Post date:** [February 24, 2019, 7:48pm UTC](https://discourse.pijul.org/t/many-errors-when-cloning-pijul-org-pijul/260/6 "2019-02-24T19:48:43Z")

</div>

> [@pmeunier](#):
>
> THIS IS FIXED! I’M SO HAPPY!

Yay! \o/

I’ll try pulling again when I get the opportunity. What was the problem?

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [February 24, 2019, 11:52pm UTC](https://discourse.pijul.org/t/many-errors-when-cloning-pijul-org-pijul/260/7 "2019-02-24T23:52:17Z")

</div>

The problem is rather hard to describe. In short, it was (1) a problem in the code that outputs the graph into a flat file, along with (2) a mismatch between that output and the new fast diff.

Diff needs to know exactly what comes out of the flattening algorithm, because it can’t really recognise where the lines come from else. Aligning the two has required more and more precision as Pijul evolved, culminating in the last failure.

My next mission for Pijul is to change the Nest to reject patches that produce conflicts. This is actually quite easy, we just need to return the number of conflicts from the apply function.

---

<div class="post-metadata">

**Author:** ![qyh](https://avatars.discourse-cdn.com/v4/letter/q/ee59a6/32.png) [@qyh](https://discourse.pijul.org/u/qyh)\
**Post date:** [April 7, 2019, 10:05am UTC](https://discourse.pijul.org/t/many-errors-when-cloning-pijul-org-pijul/260/8 "2019-04-07T10:05:09Z")

</div>

Has the fix been officially released? The latest version of Pijul from `cargo install` is 11.1 (same as before) and I’m still getting the same errors when cloning.

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [April 7, 2019, 2:03pm UTC](https://discourse.pijul.org/t/many-errors-when-cloning-pijul-org-pijul/260/9 "2019-04-07T14:03:47Z")

</div>

It has not been officially released, no, but will be very soon. There are still a few half-baked features in the master branch (PGP support is almost there, and a few stability enhancements have not been completely tested).