Skip to content
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

Open
Et7f3 opened this issue Jul 7, 2019 · 4 comments
Open

failed to lock file #79

Et7f3 opened this issue Jul 7, 2019 · 4 comments

Comments

@Et7f3
Copy link

Et7f3 commented Jul 7, 2019

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:

  • Open Node.js command prompt as a administrator.
  • Navigate with cd to esy.sh project (a folder with a package.json that can be generated by npm -init
  • esy add @esy-ocaml/utop
  • esy b utop

just after the the header is displayed I get this message:

utop.exe: lambda-term(history): failed to lock file 'C:\Users\root\AppData\Roaming\npm\node_modules\esy\node_modules\esy-bash\.cygwin\usr\esy\.utop-history': Une opération de verrouillage de fichier demandée ne peut pas être traitée en raison d’une plage d’octets non valide.
utop.exe: lambda-term(history):

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.

@pmetzger
Copy link
Member

pmetzger commented Jul 7, 2019

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.)

@DrYSG
Copy link

DrYSG commented Jan 27, 2020

I am also getting the same error. all I do is #use CommandLiner and then #use <myfile.ml> similar config

@tonykipkemboi
Copy link

Was this ever resolved? I am still getting the same error message:

utop.exe: lambda-term(history): failed to lock file 'C:\OCaml64\home\tonyk\.utop-history': A requested file lock operation cannot be processed due to an invalid byte range.
utop.exe: lambda-term(history):

@pmetzger
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants