esy install fails

[xavierzwirtz]

esy version: 0.5.8 Operating System: Windows 10

Issue: Running esy install in a fresh clone of https://github.com/esy-ocaml/hello-reason fails:

info install 0.5.8 (using package.json)
.... fetching [email protected] system cannot find the path specified.
.... fetching @opam/dune@opam:1.8.2esy: internal error, uncaught exception:
     End_of_file
     Raised at file "src/core/lwt.ml", line 2998, characters 20-29
     Called from file "src/unix/lwt_main.ml", line 26, characters 8-18
     Called from file "esy-lib/Cli.re", line 263, characters 9-28
     Called from file "cmdliner_term.ml", line 25, characters 19-24
     Called from file "cmdliner.ml", line 25, characters 27-34
     Called from file "cmdliner.ml", line 116, characters 32-39
The system cannot find the path specified.
.... fetching @opam/ocamlbuild@opam:0.14.0

Additional steps to reproduce: I am using nvm, unknown if that is the cause.

[ManasJayanth]

@xavierzwirtz I was able on run esy install on the hello-reason locally here. Maybe it was network related? In any case, can you try again with --verbosity=debug

esy install --verbosity=debug

[xavierzwirtz]

Output from esy install --verbosity=debug

debug checkStaleness C:\Projects\hello-reason\_esy\default\installation.json: false
debug checkStaleness C:\Projects\hello-reason\esy.lock\index.json: false
debug checkStaleness C:\Projects\hello-reason\package.json: false
debug using cache
debug reading project cache: 57.136059ms
info install 0.5.8 (using package.json)
debug SolutionLock.ofPath C:\Projects\hello-reason\esy.lock
debug SolutionLock.ofPath C:\Projects\hello-reason\esy.lock
debug fetching @esy-ocaml/[email protected]: installed
debug fetching @opam/base-threads@opam:base: installed
debug fetching @opam/base-unix@opam:base: installed
debug fetching [email protected]: fetching
debug fetching @opam/dune@opam:1.8.2: fetching
debug fetching @opam/ocamlbuild@opam:0.14.0: fetching
debug fetching @opam/conf-m4@opam:1: fetching
debug fetching @opam/ocamlfind@opam:1.8.0: installed
debug fetching @opam/menhir@opam:20181113: installed
debug fetching @opam/jbuilder@opam:transition: installed
debug fetching @opam/cppo@opam:1.6.5: installed
debug fetching @opam/merlin-extend@opam:0.3: installed
debug fetching @opam/ppx_derivers@opam:1.0: installed
debug fetching @opam/result@opam:1.3: installed
debug fetching @opam/ocaml-migrate-parsetree@opam:1.2.0: fetching
debug fetching @esy-ocaml/[email protected]: installed
debug fetching @opam/conf-which@opam:1: fetching
debug fetching @opam/easy-format@opam:1.3.1: fetching
debug fetching @opam/biniou@opam:1.2.0: fetching
debug fetching @opam/yojson@opam:1.7.0: fetching
debug fetching @opam/merlin@opam:3.2.2: fetching
debug fetching @opam/base-bytes@opam:base: fetching
debug fetching @opam/topkg@opam:1.0.0: fetching
debug fetching @opam/astring@opam:0.8.3: fetching
debug fetching @opam/cmdliner@opam:1.0.3: fetching
debug fetching @opam/fpath@opam:0.7.2: fetching
debug fetching @opam/seq@opam:0.1: fetching
debug fetching @opam/re@opam:1.8.0: fetching
debug fetching @opam/uchar@opam:0.0.2: fetching
debug fetching @opam/uutf@opam:1.0.2: fetching
debug fetching @opam/tyxml@opam:4.3.0: fetching
debug fetching @opam/odoc@opam:1.4.0: fetching
debug fetching @reason-native/[email protected]: fetching
debug fetching @reason-native/[email protected]: fetching
debug fetching @opam/ptime@opam:0.8.4: fetching
debug fetching @opam/junit@opam:2.0.1: fetching
debug fetching @reason-native/[email protected]: fetching
debug fetching [email protected]: fetching
debug fetching @reason-native/[email protected]: fetching
.... fetching @esy-ocaml/[email protected] system cannot find the path specified.
esy: internal error, uncaught exception:
     End_of_file
     Raised at file "src/core/lwt.ml", line 2998, characters 20-29
     Called from file "src/unix/lwt_main.ml", line 26, characters 8-18
     Called from file "esy-lib/Cli.re", line 263, characters 9-28
     Called from file "cmdliner_term.ml", line 25, characters 19-24
     Called from file "cmdliner.ml", line 25, characters 27-34
     Called from file "cmdliner.ml", line 116, characters 32-39
.... fetching @esy-ocaml/[email protected]

[devmetal]

@xavierzwirtz Same issue here. I just followed the steps from offical website, and i get the same output. Currently i tried this on a windows10 machine, but i will try at home with linux as well.

[ulrikstrid]

I can test this as well. But just to make sure, are you in a admin shell?

[xavierzwirtz]

Was not originally, re-testing with an admin instance of cmd shows the same error.

[devmetal]

I tried in admin shell to, but the results are the same

[ulrikstrid]

@xavierzwirtz @devmetal I can't reproduce the issue on my machine either. I'm using powershell as admin, what are you running?

[xavierzwirtz]

Tried in both powershell and cmd.

[devmetal]

[edited]

Yes, both. Same output. Can you @xavierzwirtz or @ulrikstrid give some advice for provide better informations. I'll be honest, i'll not planning to use esy in windows because mostly i working on linux (and in linux esy working like a dream :D) But maybe somebody using windows for evry day working and some day just run into the same thing.

So if you can show some command for better log output, i'll gladly show the results.

[klcantrell]

For me, going through the instructions from the official website on a Windows 10 machine produces the following message. I didn't get as far as the @xavierzwirtz but thought this might be the right issue to report this problem.

$ esy
/c/Users/cantr/AppData/Roaming/npm/esy: line 1: /node_modules/esy/_build/default/bin/esy.exe: No such file or directory

Going through the getting started steps on a Mac worked fine on the other hand.

[ManasJayanth]

I think your issue is slightly different: it looks like your are running it inside a cygwin shell. Can append '.cmd' and try again?

On Wed 11 Sep, 2019, 7:23 AM Kalalau Cantrell, [email protected] wrote:

For me, going through the instructions from the official website on a Windows 10 machine produces the following message. I didn't get as far as the @xavierzwirtz https://github.com/xavierzwirtz but thought this might be the right issue to report this problem.

$ esy /c/Users/cantr/AppData/Roaming/npm/esy: line 1: /node_modules/esy/_build/default/bin/esy.exe: No such file or directory

Going through the getting started steps on a Mac worked fine on the other hand.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/esy/esy/issues/967?email_source=notifications&email_token=AAXUDORDJODUWXNM2DQEG63QJBFQJA5CNFSM4IPFL64KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6M744A#issuecomment-530185840, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXUDOTGB5VN4RJBZWDA3DLQJBFQJANCNFSM4IPFL64A .

[klcantrell]

Hey that seems to work, thanks @prometheansacrifice! I was able to run esy.cmd and then run the test script and it worked.

[xavierzwirtz]

This is an issue with nvm. I uninstalled nvm, and installed node v12.11.1 directly. esy install succeeds now.

[zoubingwu]

I didn't have nvm.

$ esy --version
/c/Users/zouxi/AppData/Roaming/npm/esy: line 1: /node_modules/esy/_build/default/bin/esy.exe: No such file or directory

This happened on git bash and Windows Terminal, was fine with cmd tho.

[ManasJayanth]

@shadeofgod The issue you are facing has to do with the esy is distributed via npm - and we're working on alternatives.

git bash works similar mingw terminal - can you try appending .cmd and try as a workaround for now

[jordwalke]

Sounds like there's two different issues here:

1. Nested git-bash / cygwin environments.
2. nvm
3. @shadeofgod's issue which I don't fully understand. @prometheansacrifice what's that final issue?

[jordwalke]

Edit: I think #3 is just #1, right?

[ManasJayanth]

Yes, I think so too