Error when pushing to nst

1

When I push to my nest repo I get the follow error. The changes are pushed to next correctly, I just get this error on my local machine

Shall I push this patch? [ynkad?] y
thread ‘main’ panicked at ‘called Result::unwrap() on an Err value: Error(IO(Custom { kind: UnexpectedEof, error: “early eof” }))’, src/libcore/result.rs:999:5
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace.

does anyone else get this problem?

Thanks

2

thread ‘main’ panicked at ‘called Result::unwrap() on an Err value: Error(IO(Custom { kind: UnexpectedEof, error: “early eof” }))’, /home/ciaran/.cargo/registry/src/github.com-1ecc6299db9ec823/pijul-0.12.2/src/commands/remote.rs:543:13
stack backtrace:
0: 0x56535f621084 - backtrace::backtrace::libunwind::trace::h90669f559fb267f0
at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
1: 0x56535f621084 - backtrace::backtrace::trace_unsynchronized::hffde4e353d8f2f9a
at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
2: 0x56535f621084 - std::sys_common::backtrace::_print_fmt::heaf44068b7eaaa6a
at src/libstd/sys_common/backtrace.rs:77
3: 0x56535f621084 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h88671019cf081de2
at src/libstd/sys_common/backtrace.rs:59
4: 0x56535f64744c - core::fmt::write::h4e6a29ee6319c9fd
at src/libcore/fmt/mod.rs:1052
5: 0x56535f619c17 - std::io::Write::write_fmt::hf06b1c86d898d7d6
at src/libstd/io/mod.rs:1426
6: 0x56535f623905 - std::sys_common::backtrace::_print::h404ff5f2b50cae09
at src/libstd/sys_common/backtrace.rs:62
7: 0x56535f623905 - std::sys_common::backtrace::print::hcc4377f1f882322e
at src/libstd/sys_common/backtrace.rs:49
8: 0x56535f623905 - std::panicking::default_hook::{{closure}}::hc172eff6f35b7f39
at src/libstd/panicking.rs:204
9: 0x56535f6235f1 - std::panicking::default_hook::h7a68887d113f8029
at src/libstd/panicking.rs:224
10: 0x56535f623f6a - std::panicking::rust_panic_with_hook::hb7ad5693188bdb00
at src/libstd/panicking.rs:472
11: 0x56535f623b50 - rust_begin_unwind
at src/libstd/panicking.rs:380
12: 0x56535f645c61 - core::panicking::panic_fmt::hb1f3e14b86a3520c
at src/libcore/panicking.rs:85
13: 0x56535f645a83 - core::option::expect_none_failed::he6711468044f7162
at src/libcore/option.rs:1199
14: 0x56535f15123d - pijul::commands::remote::Session::push::h6430be04007fa8ae
15: 0x56535f10f6c1 - pijul::commands::push::run::h98d52317c3f0ecd2
16: 0x56535f157e24 - pijul::main::h49b5b8bd387d5fed
17: 0x56535f12e2a3 - std::rt::lang_start::{{closure}}::h612e1d484debb498
18: 0x56535f623a33 - std::rt::lang_start_internal::{{closure}}::hb26e39676675046f
at src/libstd/rt.rs:52
19: 0x56535f623a33 - std::panicking::try::do_call::he4701ab6e48d80c0
at src/libstd/panicking.rs:305
20: 0x56535f62d7e7 - __rust_maybe_catch_panic
at src/libpanic_unwind/lib.rs:86
21: 0x56535f6244d0 - std::panicking::try::hd3de25f3cb7024b8
at src/libstd/panicking.rs:281
22: 0x56535f6244d0 - std::panic::catch_unwind::h86c02743a24e3d92
at src/libstd/panic.rs:394
23: 0x56535f6244d0 - std::rt::lang_start_internal::h9cf8802361ad86c2
at src/libstd/rt.rs:51
24: 0x56535f1611b2 - main
25: 0x7f34992c71a3 - __libc_start_main
26: 0x56535ee1127e - _start
27: 0x0 -

3

I have updated to the latest versions of rust, cargo and pijul, but I am still getting this error. Does anyone have any idea how I am cauing this?

~/Documents/rust_api_crud_example  $ cargo version                                                                                                                                                                                      101 ↵
cargo 1.42.0 (86334295e 2020-01-31)
~/Documents/rust_api_crud_example  $ rustc --version              
rustc 1.42.0 (b8cedc004 2020-03-09)
~/Documents/rust_api_crud_example  $ pijul --version                                                                                                                                                                                      1 ↵
pijul 0.12.2