You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am getting checksum does not match aborting! every time I call lingo build. If I try removing Lingo.lock and rerun lingo build I get:
thread 'main' panicked at src/package/management.rs:153:14:
creating lock folder failed: Permission denied (os error 13)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
This produces a new Lingo.lock and if I run lingo build again, I don't get a panic but back to checksum does not match aborting!
When I remove both Lingo.lock and build, then I can run lingo build without the error. But only then first run, every proceeding run gets the checksum error.
It seems:
lingo clean should probably remove the build folder?
The checksum calculation might happen at the wrong point? And should we actually abort?
The text was updated successfully, but these errors were encountered:
This is strange, so I save the hash of all files in this library in the file Lingo.lock and before I call lfc again, I check if the hash is still the same or if someone/something has tampered with it.
Either there is a problem with the implementation or some of the files have really changed.
I am getting
checksum does not match aborting!
every time I calllingo build
. If I try removing Lingo.lock and rerunlingo build
I get:This produces a new
Lingo.lock
and if I runlingo build
again, I don't get a panic but back tochecksum does not match aborting!
When I remove both Lingo.lock and build, then I can run
lingo build
without the error. But only then first run, every proceeding run gets the checksum error.It seems:
lingo clean
should probably remove thebuild
folder?The text was updated successfully, but these errors were encountered: