The sound distributed version control system

#515 pijul Crash Report: switching channels

Opened by fintohaps on August 16, 2021
fintohaps on August 16, 2021

The events that led up to this crash were:

  1. I wanted to unrecord a change, but it had dependencies so the command threw an error
  2. I forked a new channel to see if I could play with unrecording and reapplying changes
  3. When I tried to channel switch to the new channel it threw this error
  4. I was able to switch to main but now I can’t switch back to the channel I was working on.
name = 'pijul'
operating_system = 'unix:Unknown'
crate_version = '1.0.0-alpha.49'
explanation = '''
Panic occurred in file '/home/haptop/.cargo/registry/src/github.com-1ecc6299db9ec823/libpijul-1.0.0-alpha.43/src/fs.rs
' at line 872
'''
cause = '''
assertion failed: `(left == right)`
  left: `V(ChangeId(2VPS4FCPBPQ3U)[0:40])`,
 right: `V(ChangeId(2VPS4FCPBPQ3U)[31:31])`'''
method = 'Panic'
backtrace = '''

   0: 0x5606af60b939 - libpijul::fs::find_path::h2dcd1cb0a46c783c
   1: 0x5606af6b4039 - pijul::commands::reset::Reset::reset::{{closure}}::hf40bc139c3acf6f4
   2: 0x5606af6e13be - pijul::run::{{closure}}::h9b619a78829b1794
   3: 0x5606af68b71b - <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::hd917dca976
0df1ff
   4: 0x5606af56b24f - tokio::park::thread::CachedParkThread::block_on::had630c3f121fcc91
   5: 0x5606af7318f2 - tokio::runtime::Runtime::block_on::he5a969ee7d451684
   6: 0x5606af638b66 - pijul::main::hdaf525957228bc48
   7: 0x5606af64b623 - std::sys_common::backtrace::__rust_begin_short_backtrace::h6ca42d0d9e806da1
   8: 0x5606af611029 - std::rt::lang_start::{{closure}}::h94412df04438c44f
   9: 0x5606afcaa567 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h57e2a071d
427b24c
                at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/ops/function.rs:259
                 - std::panicking::try::do_call::h81cbbe0c3b30a28e
                at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panicking.rs:381
                 - std::panicking::try::hbeeb95b4e1f0a876
                at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panicking.rs:345
                 - std::panic::catch_unwind::h59c48ccb40a0bf20
                at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panic.rs:396
                 - std::rt::lang_start_internal::ha53ab63f88fee728
                at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/rt.rs:51
  10: 0x5606af638c22 - main
  11: 0x7fa3b8516ded - __libc_start_main
  12: 0x5606af43e2ba - _start
                at /build/glibc-2.32/csu/../sysdeps/x86_64/start.S:120
  13:        0x0 - <unresolved>'''
pmeunier on August 16, 2021

I’d be interested if you can send a tarball of your .pijul to pe@pijul.org

pmeunier on August 16, 2021

Wait, it seems you’re using a rather old version of Pijul, and your bug looks like a corruption error. Several bugs have been found in Sanakirja since that version, I encourage you to try and reproduce with the latest version of Pijul.