Yesterday I ran
cargo update and then
cargo build. It downloaded some updated crates and was building pijil, when almost at the end, it errored out and I realized I had not pulled down the latest pijul. Cargo had output that it was waiting for some processes to finish. So I typed in
pijul pull and it showed some changes. I used Ctrl X to exit the editor (I still don’t like that interface!) and it completed.
When I tried
cargo build again, it immediately said there were invalid characters in Cargo.lock. I looked at the file, and sure enough, there were lines of
------------------- looking like conflict markers. I tried
pijul pull again, but it said there was nothing to pull.
So I went to the Nest and looked at the file. It’s crazy that it’s 2559 lines! I copied that one to my local copy, and the build worked fine. (by the way, the Nest doesn’t have any easy way to copy a file)
So my question is, why was that file corrupted that way? I know it’s dynamically generated, but did Pijul not detect the difference between the local and remote?
And why is that file so big? (there are multiple versions of lots of crates referenced in there)