This scenario is ok.

It passed.

For now release target of latest pijul built with debug command, if run pijul debug inside repo2 dir it crashes.

$ cat /tmp/report-df5b414b-5d9f-4102-8370-c1056711be43.toml
name = 'pijul'
operating_system = 'unix:Unknown'
crate_version = '1.0.0-alpha.48'
explanation = '''
Panic occurred in file '/home/mpech/.cargo/registry/src/github.com-1ecc6299db9ec823/sanakirja-1.2.0/src/debug.rs' at line 201
'''
cause = 'page not found: 0xc25000 (total length 0x56a6000)'
method = 'Panic'
backtrace = '''

   0: 0x560408bffbdb - sanakirja::debug::check_free::h91f565e91d7d1dd1
   1: 0x560408c81347 - libpijul::pristine::sanakirja::GenericTxn<sanakirja::environment::Txn<alloc::sync::Arc<sanakirja::environment::Env>>>::check_database::ha26da88aebfc5692
   2: 0x560408974ac0 - pijul::run::{{closure}}::h1addda3139a1a578
   3: 0x56040890e3e8 - <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h17c33ee9c519857f
   4: 0x56040874ce72 - tokio::runtime::thread_pool::ThreadPool::block_on::h08771bb26e14a89a
   5: 0x5604088e8ac0 - tokio::runtime::Runtime::block_on::h0a6547192b68156a
   6: 0x5604088a71b6 - pijul::main::h6ddd0222d5aa7776
   7: 0x560408884b63 - std::sys_common::backtrace::__rust_begin_short_backtrace::hcd09ee0b4eeec1e8
   8: 0x560408884f99 - std::rt::lang_start::{{closure}}::h41872dd1011dfad7
   9: 0x560408ebe0e8 - std::rt::lang_start_internal::h35b6f595e94b11f4
  10: 0x5604088a7272 - main
  11: 0x7f58331c4a03 - <unresolved>'''
delta:~/vimX $ 

At the same time if run pijul debug inside repo2 dir from picolispX it prints the tree without crash.

a broken (?) repo is here (tar.xz).

This is source TAR.XZ repo of minimum required first 500 commits from 12K.

pijul debug will be ok here and crash after clone from it.

Still here after today’s fixes.

Lets call this is latest sanakirja’s bug.

A very easy and fast to repeat:

$ cd 
$ git clone https://github.com/vim/vim.git
# clone of pull latest vimX (https://nest.pijul.com/tankf33der/vimX)
$ cd vimX
$ ./runme.sh
# CRASH in 'pijul debug' insider repo2 dir
$

Seems it fixed now.