This happend directly after the crash from #208 by running pijul reset

After looking at the terminal log again it appears to have instead been caused by pijul record.

name = 'pijul'
operating_system = 'unix:Unknown'
crate_version = '1.0.0-alpha.21'
explanation = '''
Panic occurred in file '/home/bennet/.cargo/registry/src/github.com-1ecc6299db9ec823/libpijul-1.0.0-alpha.18/src/change/text_changes.rs' at line 1090
'''
cause = 'called `Option::unwrap()` on a `None` value'
method = 'Panic'
backtrace = '''

   0: 0x55af55dc8e7d - core::panicking::panic::h184ede6dd822ffb4
                at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/panicking.rs:50
   1: 0x55af55a6f507 - libpijul::change::text_changes::change_ref::h588f6cbf36562421
   2: 0x55af55a6f5f0 - libpijul::change::text_changes::parse_pos::hb47a0d5ac2ab4430
   3: 0x55af55a50cb0 - libpijul::change::text_changes::,libpijul::change::Local>>::read::h4aaea586021a63ca
   4: 0x55af5560393e - libpijul::change::text_changes::>::read_and_deps::h99dfa6020f6327ff
   5: 0x55af555f4cd7 - pijul::commands::record::Record::record::hbc981c84a39d64e5
   6: 0x55af557b0798 - pijul::commands::record::Record::run::{{closure}}::h1b5a42de1193ae1d
   7: 0x55af55799fb3 -  as core::future::future::Future>::poll::hd58a59fad351c664
   8: 0x55af555efc50 - tokio::runtime::enter::Enter::block_on::h5c5f0c236d76dc6b
   9: 0x55af556aef6d - tokio::runtime::thread_pool::ThreadPool::block_on::hdf8498896066a38e
  10: 0x55af5568f3cc - tokio::runtime::context::enter::h203b49ab005ba120
  11: 0x55af555ff645 - pijul::main::h38d1b94d672dc695
  12: 0x55af5572bed3 - std::sys_common::backtrace::__rust_begin_short_backtrace::ha6f34f232102fef1
  13: 0x55af55677509 - std::rt::lang_start::{{closure}}::h06cbf468ee028a2f
  14: 0x55af55da5e97 - core::ops::function::impls:: for &F>::call_once::he179d32a5d10d957
                at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:259
                 - std::panicking::try::do_call::hcb3d5e7be089b2b4
                at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:381
                 - std::panicking::try::h7ac93b0cd56fb701
                at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:345
                 - std::panic::catch_unwind::h7b40e396c93a4fcd
                at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panic.rs:382
                 - std::rt::lang_start_internal::h142b9cc66267fea1
                at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/rt.rs:51
  15: 0x55af555ff772 - main
  16: 0x7f1be16dc0b3 - __libc_start_main
  17: 0x55af5559d2ce - _start
  18:        0x0 - '''

Hi! This is interesting, thanks for reporting. Unfortunately, I can’t reproduce. Would you mind pasting the change in text format here, or sending it to pe@pijul.org?

I wish I could do that but I no longer have them. I also had a look at the terminal log that I saved again and noticed that I mentioned the wrong command above, the crash happend while running pijul record not pijul reset.

I think that I tried to change the dependencies of the change during pijul record and messed that up.

I am able to reproduce this with the following steps:

1. Init new pijul repository
2. Add a file and record a change
3. Edit the file
4. While recording a new change edit the # Dependencies Section e.g. change

# Dependencies
[2] 6OJHNZD6A7FAGSW7NR4IM3JXPBTJDPDWQKBSQMQ3KMADHX76WKGAC

to

# Dependencies
[ ] 6OJHNZD6A7FAGSW7NR4IM3JXPBTJDPDWQKBSQMQ3KMADHX76WKGAC

I fixed this. This is poorly documented at the moment (changes to the manual welcome!), but you’re not supposed to touch numbered dependencies. Also, the following is invalid syntax:

[ ] 6OJHNZD6A7FAGSW7NR4IM3JXPBTJDPDWQKBSQMQ3KMADHX76WKGAC

Because there is a space between [ and ].