I discovered this when I tried to use a unique prefix instead of a full hash, like in Git.
Version: pijul 0.7.3 (from cargo)
Running pijul unrecord --patch 0 in a repository causes a panic:
pijul unrecord --patch 0
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/libcore/option.rs:335:20
I've found the issue and am working on a fix. It looks like base64 validation on the command-line isn't done consistently.
Good catch! Thanks a lot for reporting this. If you need any help while writing a fix, feel free to ask.
I've added a base64 validator in the places I could find that needed it, in this patch. (The "Add Patches" button doesn't seem to work?)
Great patch! I fixed the Nest yesterday for this kind of cases, and merged your patch just now.