v0.8.0 installation not working on windows

[littleskunk]

First Problem on windows is this line: https://github.com/littleskunk/storjshare-gui/blob/master/package.json#L29

I had to changed env HOME=~/.electron-gyp to set HOME=%userprofile%/.electron-gyp. That way I was able to install it but not able to build a binary. The path is to long for windows.

File: failed opening file "C:\storjshare-gui\tmp\storjshare\resources\app\node_modules\storj\node_modules\leveldown\node_modules\prebuild\node_modules\ghreleases\node_modules\ghutils\node_modules\jsonist\node_modules\bl\node_modules\readable-stream\node_modules\core-util-is\package.json"

[littleskunk]

flatten-packages and npm3 are not the solution or it is a new issue.

npm start looks good but after installing the binary I have this:

[44203]

what's in the developer tools log?

[littleskunk]

Expected output (npm start):

[Vue warn]: Error when evaluating expression "tab.active": TypeError: Cannot read property 'active' of undefinedwarn @ C:\storjshare-gui\build\node_modules\vue\dist\vue.common.js:1014
C:\storjshare-gui\build\node_modules\vue\dist\vue.common.js:10025 Download the Vue Devtools for a better development experience:
https://github.com/vuejs/vue-devtools

Actual output (start binary):

Uncaught Error: EPERM: operation not permitted, write
C:\Program Files (x86)\Storj Share\resources\app\node_modules\vue\dist\vue.common.js:10025 Download the Vue Devtools for a better development experience:
https://github.com/vuejs/vue-devtools

It looks like flatten-packages is working but we have a new bug. Something is wrong with the NSIS. I will try to get a full log or any other usefull information.

[littleskunk]

electron/electron#2033

Reason for this error: stdout somewhere in the code. I will find it. We are so close :)

I am able to start the binary out of a cmd window. That way it has stdout.

https://github.com/Storj/core/blob/948a2c6e50e64e87a7f30b6ecc0e8305def301b2/bin/bridgecli.js#L570
https://github.com/Storj/core/blob/948a2c6e50e64e87a7f30b6ecc0e8305def301b2/bin/bridgecli.js#L567

[littleskunk]

No that was not the problem or maybe not the only problem. I will keep the core pull request open. Debuging with the developer console gives me a full stack trace.

Uncaught Error: EPERM: operation not permitted, writefs.writeSync @ fs.js:706SyncWriteStream.write @ fs.js:2059execSync @ child_process.js:514_diskSpace @ C:\Program Files (x86)\Storj Share\resources\app\node_modules\fd-diskspace\bin\index.js:119diskSpaceSync @ C:\Program Files (x86)\Storj Share\resources\app\node_modules\fd-diskspace\bin\index.js:171Vue.methods.getFreeSpace @ client.js:473(anonymous function) @ C:\Program Files (x86)\Storj Share\resources\app\node_modules\vue\dist\vue.common.js:216Vue.methods.showTab @ client.js:233(anonymous function) @ C:\Program Files (x86)\Storj Share\resources\app\node_modules\vue\dist\vue.common.js:216Vue.created @ client.js:568Vue._callHook @ C:\Program Files (x86)\Storj Share\resources\app\node_modules\vue\dist\vue.common.js:8199Vue._init @ C:\Program Files (x86)\Storj Share\resources\app\node_modules\vue\dist\vue.common.js:2453Vue @ C:\Program Files (x86)\Storj Share\resources\app\node_modules\vue\dist\vue.common.js:9474(anonymous function) @ client.js:153

The problem: https://github.com/SuperPaintman/fd-diskspace/blob/b49bee82e3432e8bd53850a2f879e5196d6835af/bin/index.js#L119

@bookchin What now? I don't know how to fix this.

[44203]

Ughhh.... This happened with the last disk space issue too. For whatever reason, one the binary is packaged, it doesn't have permission to execute the command to get the diskspace.

[44203]

Which I have no idea how to fix Windows crazy permissions system or why a userland application is not allowed to execute a user permissioned command.

[44203]

https://stackoverflow.com/questions/34982443/eperm-error-in-nodejs-when-calling-execsync

?

[44203]

If that fixes it I guess we can fork that fd-diskspace module and change it.

[littleskunk]

If I start the binary from the comand line it is attached to the stdout of that command line. Everything is running fine. No permission problem.

The Problem is that executing the exe file will not attach any stdout. Only console.log and console.error are allowed.

Your link looks good. I will try it. We don't need to fork fd-diskspace if that is working. The codechange would effect storjshare-gui only.

[littleskunk]

Fixed and open pull request for fd-diskspace. Switched to my fork as long as the pull request is not merged.