Pijul repo server is down?

Question
1

It seems that I cannot clone it this morning (I could last night though):

$ pijul clone https://nest.pijul.com/pijul_org/pijul
error: https://nest.pijul.com/pijul_org/pijul/.pijul/changes.wUAdAoNq: Connection refused (os error 111)

$ pijul clone https://nest.pijul.com/pijul_org/pijul
error: https://nest.pijul.com/pijul_org/pijul/.pijul/changes.wUAdAoNq: The underlying stream reported an error: unexpected EOF observed

$ pijul clone https://nest.pijul.com/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Io(Error { repr: Custom(Custom { kind: Other, error: Stream(Error { repr: Os { code: 104, message: "Connection reset by peer" } }) }) }), url: Some("https://nest.pijul.com/pijul_org/pijul/.pijul/patches/A5hSHwCvpMMKt1m38JgTk95eBscejcqn1Usg2SnMhM9kbnvgJPcFQnGbGLtwivBVcSu2Mfu3JkoMu1nZeik8BVf7.gz") }', src/libcore/result.rs:906:1234:

$ pijul clone https://nest.pijul.com/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Io(Error { repr: Custom(Custom { kind: Other, error: Stream(Error { repr: Custom(Custom { kind: ConnectionAborted, error: StringError("unexpected EOF observed") }) }) }) }), url: Some("https://nest.pijul.com/pijul_org/pijul/.pijul/patches/9LuhZfDXZscfFAWnS1vm7JmPtuFzdskY9xf7VAs87G3LwvwXgZLJ2qSCxjTh4C1tojBVmtnFC9QhG95y33iKnA9w.gz") }', src/libcore/result.rs:906:4

note: Run with RUST_BACKTRACE=1 for a backtrace.

Interestingly each time the error message seems different :slight_smile:

2

Still seeing the error tonight:

$ pijul clone https://nest.pijul.com/pijul_org/pijul
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Io(Error { repr: Os { code: 111, message: "Connection refused" } }), url: Some("https://nest.pijul.com/pijul_org/pijul/.pijul/patches/6onYJreK1H4o3WHBtyYczSdBoKLrkDyhuwwBaatCFPDLxBf9qjEE3TpTU7g2kSWtYiJjQUxs4Go2mmc948LDw1kS.gz") }', src/libcore/result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Using a latest version just installed via the command cargo install --force pijul tonight.

3

It seems you may have missed this announcement.

4

Thanks for the reminder. Sorry that I forgot to mention that I indeed tried pijul 0.8.3 that day via cargo but the same error persisted every time I tried pijul clone https://nest.pijul.com/pijul_org/pijul from scratch. The “connection refused” thing looks very much like a server side bug since network issues should result in errors like “connection timed out” or “connection reset by peer”.

5

The nest is using libpijul-0.9. If you try to use it with pijul-0.9, it will work just fine. Unfortunately, pijul-0.9 is flawed and you might record incorrect patches.

You can easily use pijul-0.8.3 with your own server, but not with the nest at the moment :\.