Open Mbodin opened 4 years ago
Hi, this is not the bug with caching so removing any caches won't solve it. It's a bug with dependency solver. cc @zindel (as you've touched the solver code recently) any clues on that?
Thanks for the answer ☺
As an additional note, running the following commands did not change the behaviour:
$ sudo npm uninstall -g esy
$ sudo npm install -g esy@latest
esy version: 0.6.4 Operating System: Ubuntu 18.04.4
Issue: I am working on this small repository: https://github.com/Mbodin/dune-bug/tree/91d1f7039685e9bb5777e19e2335f9f75284b797 After a lot of work with esy, I reached an inconsistent state. To solve the inconsistent state, I removed the folders
~/.esy
,_esy
,node_modules
, andesy.lock
. Unfortunately, esy then complained with the error message shown below. Is there another folder that I should have removed? 😕​Package.json https://github.com/Mbodin/dune-bug/blob/91d1f7039685e9bb5777e19e2335f9f75284b797/package.json
Actual behavior:
Expected behavior: I would have expected that removing these folders would have made esy fresh as new.