A Weird Bug with Pijul

Question
1

I’m getting this error:

What is the name of this patch? thread ‘main’ panicked at ‘called Result::unwrap() on an Err value: Custom { kind: UnexpectedEof, error: StringError(“failed to fill whole buffer”) }’, src/libcore/result.rs:997:5
note: Run with RUST_BACKTRACE=1 environment variable to display a backtrace.

I don’t know if it’s a coincidence or not that this is my very longest patch I’ve done thus far and the first time seeing this error.

2

Backtrace:

What is the name of this patch? thread ‘main’ panicked at ‘called Result::unwrap() on an Err value: Custom { kind: UnexpectedEof, error: StringError(“failed to fill whole buffer”) }’, src/libcore/result.rs:997:5
stack backtrace:
0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
at src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:39
1: std::sys_common::backtrace::_print
at src/libstd/sys_common/backtrace.rs:70
2: std::panicking::default_hook::{{closure}}
at src/libstd/sys_common/backtrace.rs:58
at src/libstd/panicking.rs:200
3: std::panicking::default_hook
at src/libstd/panicking.rs:215
4: std::panicking::rust_panic_with_hook
at src/libstd/panicking.rs:478
5: std::panicking::continue_panic_fmt
at src/libstd/panicking.rs:385
6: rust_begin_unwind
at src/libstd/panicking.rs:312
7: core::panicking::panic_fmt
at src/libcore/panicking.rs:85
8: core::result::unwrap_failed
9: pijul::commands::ask::read_line
10: pijul::commands::ask::ask_patch_name
11: pijul::commands::record::decide_patch_message
12: pijul::commands::record::run
13: pijul::main
14: std::rt::lang_start::{{closure}}
15: std::panicking::try::do_call
at src/libstd/rt.rs:49
at src/libstd/panicking.rs:297
16: __rust_maybe_catch_panic
at src/libpanic_unwind/lib.rs:87
17: std::rt::lang_start_internal
at src/libstd/panicking.rs:276
at src/libstd/panic.rs:388
at src/libstd/rt.rs:48
18: main
19: __libc_start_main
20: _start
at …/sysdeps/x86_64/start.S:120

3

Restarting my computer worked for some reason. So idk…