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

Storing configuration within OneDrive is not supported #2835

Open
2 tasks done
josephst opened this issue Apr 16, 2018 · 1 comment
Open
2 tasks done

Storing configuration within OneDrive is not supported #2835

josephst opened this issue Apr 16, 2018 · 1 comment
Labels
help wanted Contributions wanted towards the issue 👆 Is Upstream Issue is the fault of something Hyper uses and not Hyper itself 🖼 Platform: Windows Issue pertains to Windows 🤯 Type: Compatibility Issue contains information about a compatibility issue in Hyper

Comments

@josephst
Copy link

  • I am on the latest Hyper.app version
  • I have searched the issues of this repo and believe that this is not a duplicate

Issue

With Hyper 2.0.0 on Windows 10, storing the .hyper.js configuration file in OneDrive with Files On Demand is not supported. Attempting to run commands such as hyper i hyper-snazzy returns the following error:

Error: EINVAL: invalid argument, fstat
    at tryStatSync (fs.js:519:13)
    at Object.fs.readFileSync (fs.js:555:3)
    at Object.fs.readFileSync (ELECTRON_ASAR.js:508:29)
    at memoize (C:\Users\Joseph\AppData\Local\hyper\app-2.0.0\resources\bin\cli.js:19124:15)
    at d (C:\Users\Joseph\AppData\Local\hyper\app-2.0.0\resources\bin\cli.js:19118:22)
    at Object.exists (C:\Users\Joseph\AppData\Local\hyper\app-2.0.0\resources\bin\cli.js:19138:10)
    at checkConfig (C:\Users\Joseph\AppData\Local\hyper\app-2.0.0\resources\bin\cli.js:9924:11)
    at Args.args.command (C:\Users\Joseph\AppData\Local\hyper\app-2.0.0\resources\bin\cli.js:9940:3)
    at Args.runCommand (C:\Users\Joseph\AppData\Local\hyper\app-2.0.0\resources\bin\cli.js:11309:37)
    at Args.module.exports [as parse] (C:\Users\Joseph\AppData\Local\hyper\app-2.0.0\resources\bin\cli.js:15080:10)

The issue is resolved by disabling OneDrive's Files On Demand feature. The problem lies with libuv; it was fixed in v1.14.0. Node > 8.5.0 has the fixed version of libuv, but with Electron lagging behind Node, it doesn't look like this issue will be fixed until Electron 2.0 is released (looks like Node v8.9.3 will be included in that release).

For more details about the problem, see this issue thread from Node.js.

For those affected by this issue: turning off OneDrive's Files On Demand feature will fix the problem. Once Hyper starts using Electron 2.0 following its release, this issue should be fixed for good.

@timothyis timothyis added help wanted Contributions wanted towards the issue 🤯 Type: Compatibility Issue contains information about a compatibility issue in Hyper 🖼 Platform: Windows Issue pertains to Windows labels Apr 16, 2018
@chabou
Copy link
Collaborator

chabou commented Apr 16, 2018

@josephst thank you so much for your detailed feedback 🙏

@albinekb albinekb added the 👆 Is Upstream Issue is the fault of something Hyper uses and not Hyper itself label Apr 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Contributions wanted towards the issue 👆 Is Upstream Issue is the fault of something Hyper uses and not Hyper itself 🖼 Platform: Windows Issue pertains to Windows 🤯 Type: Compatibility Issue contains information about a compatibility issue in Hyper
Projects
None yet
Development

No branches or pull requests

4 participants