Thanks (and welcome here!). If you remember (or timed it), how long did it take to reach that state?
I timed it this time:
$ time ~/pijul/target/debug/pijul git .
thread 'main' panicked at 'assertion failed: is_alive(txn, channel, &c).unwrap()', /home/jonathan/pijul/libpijul/src/apply.rs:795:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
________________________________________________________
Executed in 183,60 secs fish external
usr time 175,21 secs 5,00 micros 175,21 secs
sys time 4,26 secs 361,00 micros 4,26 secs
It takes a long time, I found myself that this repo had a lot of binaries a long time ago, nothing big, just very tiny binaries that was deleted in newer revisions, also this repo has some “empty commits” (10 to be exact), they has different hashes but the file contents haven’t changed, maybe the file permissions changed, but I’m not sure. Hope this helps with the context.
183s isn’t a very long time. A few months ago I had to wait for many days to see a crash! I’ll take a look this week-end.
I can’t imagine how it is to keep something running for days, I like how Pijul is envolving as time goes by and I’m loving it (I’m even writing an IntelliJ IDEA plugin for it), let me know if you need some additional input, and thanks for the attention!!!
5SLOJYHGPMZVCOE3IS7ICNMJJYX3RBT6CDG5MAV6T4CJIOW7YZ6QC
Alright, I fixed a few things in a number of places in Pijul since this bug, and tested pijul git
on Kores again. It works now, I could import the entire history.
Awesome, thanks for the attention, now I was able to import the entire Kores history as well.
I’ve recently discovered that Pijul is able to import git repositories when compiled with
git
feature, so I cloned the pijul repository and compiled with the git feature enabled, I’ve successfully converted some git repositories into Pijul with the exception of some bigger ones, which causes Pijul to crash with the following error:One of the repositories I was trying to convert is Kores.