-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failed to lock file #79
Comments
Can you find a simpler way to reproduce this? I don't think any of the maintainers are in a position to try that out. (I personally have no windows machine and never touch esy.) |
I am also getting the same error. all I do is #use CommandLiner and then #use <myfile.ml> similar config |
Was this ever resolved? I am still getting the same error message:
|
It was never resolved, I think because none of the maintainers are using node.js, esy, or Windows. It will be necessary for someone who is using those tools together to try to track down what has gone wrong and to supply a patch. |
OS Microsoft Windows 10 Familly
Version 10.0.17134 Number 17134
Node.js 10.15.3 (x64) and npm
esy 0.5.8
Welcome to utop version 2.4.0 (using OCaml version 4.08.0)!
step to reporduce:
Node.js command prompt
as a administrator.cd
to esy.sh project (a folder with a package.json that can be generated bynpm -init
just after the the header is displayed I get this message:
I haven't opened a issue in utop because I see
lambda-term
.Feel free to ask more information or ask me to test some other command.
The text was updated successfully, but these errors were encountered: