Jibo SDK installation fail

Hi guys.
I have a problem of JIBO SDK installation fail.
I guess this problem is caused from fire-wall of my netwok environment.

Anyway Can anyone help to solve this problem?

My problem is like below,
OS : Windows7

My apm version
C:\Users\admin>apm -v
apm 1.9.2
npm 2.13.3
node 0.10.40
python 2.7.8
git 1.9.5.github.0
visual studio 2013

And I have changed my .apmrc file to avoid fire-wall work-around. Added below configureration

Installing “jibo-sdk@1.7.1” failed.Hide output…

electron-prebuilt-reentrant@0.34.1-0 postinstall C:\Users\admin\AppData\Local\Temp\apm-install-dir-11653-9180-8glv1x\node_modules\jibo-sdk\node_modules\jibo-tools\node_modules\electron-prebuilt-reentrant
node install.js

Downloading electron-v0.34.1-win32-ia32.zip
[> ] 0.0% (0 B/s)
e[1000De[0Ke[1Ae[1000De[0Ke[1Ae[1000De[0KDownloading electron-v0.34.1-win32-ia32.zip

npm WARN engine escodegen@1.8.0: wanted: {“node”:">=0.12.0"} (current: {“node”:“0.10.40”,“npm”:“2.13.3”})
npm WARN engine gzip-size@3.0.0: wanted: {“node”:">=0.12.0"} (current: {“node”:“0.10.40”,“npm”:“2.13.3”})
npm WARN deprecated graceful-fs@3.0.8: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use ‘npm ls graceful-fs’ to find it in the tree.
npm WARN addRemoteGit Error: Command failed:
npm WARN addRemoteGit at ChildProcess.exithandler (child_process.js:658:15)
npm WARN addRemoteGit at ChildProcess.emit (events.js:98:17)
npm WARN addRemoteGit at maybeClose (child_process.js:766:16)
npm WARN addRemoteGit at Socket. (child_process.js:979:11)
npm WARN addRemoteGit at Socket.emit (events.js:95:17)
npm WARN addRemoteGit at Pipe.close (net.js:466:12)
npm WARN addRemoteGit git+https://github.com/jiborobot/pixi.js.git#dev resetting remote C:\Users\admin.atom.apm_git-remotes\https-github-com-jiborobot-pixi-js-git-786b02d9 because of error: { [Error: Command failed: ] killed: false, code: 1, signal: null }
npm ERR! git clone --template=C:\Users\admin.atom.apm_git-remotes_templates --mirror https://github.com/jiborobot/pixi.js.git C:\Users\admin.atom.apm_git-remotes\https-github-com-jiborobot-pixi-js-git-786b02d9: Cloning into bare repository ‘C:\Users\admin.atom.apm_git-remotes\https-github-com-jiborobot-pixi-js-git-786b02d9’…
npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
npm WARN engine deep-extend@0.4.1: wanted: {“node”:">=0.12.0",“iojs”:">=1.0.0"} (current: {“node”:“0.10.40”,“npm”:“2.13.3”})

throw err
npm WARN engine is-buffer@1.1.3: wanted: {“node”:">=0.12"} (current: {“node”:“0.10.40”,“npm”:“2.13.3”})
npm WARN engine is-buffer@1.1.3: wanted: {“node”:">=0.12"} (current: {“node”:“0.10.40”,“npm”:“2.13.3”})
npm ERR! Windows_NT 6.1.7601
npm ERR! argv “C:\Users\admin\AppData\Local\atom\app-1.7.4\resources\app\apm\bin\node.exe” “C:\Users\admin\AppData\Local\atom\app-1.7.4\resources\app\apm\node_modules\npm\bin\npm-cli.js” “–globalconfig” “C:\Users\admin\.atom\.apm\.apmrc” “–userconfig” “C:\Users\admin\.atom\.apmrc” “install” “C:\Users\admin\AppData\Local\Temp\d-11653-9180-1pbrp7v\package.tgz” “–target=0.36.8” “–arch=ia32” "–msvs_version=2013"
npm ERR! node v0.10.40
npm ERR! npm v2.13.3
npm ERR! code 128

npm ERR! Command failed: Cloning into bare repository ‘C:\Users\admin.atom.apm_git-remotes\https-github-com-jiborobot-pixi-js-git-786b02d9’…
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

Hey @DunkinLee
Officially, they don’t support Win7 - I’m just not sure if this is really an atom/electron issue though… I do have it running well on mac and both Win7 + 10.
I expect that one day, my Win7 installation will not work… I lost it for a few months on Win7 already after a previous sdk release - after Atom updated to 1.7.2, then the Win7 jibo sdk started working again! So I am a bit suspicious of other atom or electron issues confusing us in the future.

Given all that, your installation is similar to mine under Win7

apm -v
apm 1.9.2
npm 2.13.3
node 0.10.40
python 2.7.10
git 2.7.0.windows.1
visual studio 2013

I’ve had install failures in the past and I’ve even reinstalled atom as well.

I’ve seen the electron-prebuilt-reentrant reported in the atom issues as well, but I can’t say how the fault occurs by the jibo sdk install.
https://github.com/electron-userland/electron-prebuilt/issues/102 (reported by a Jibo team member)

Also, subsequent to a jibo SDK failure, I make sure to uninstall the SDK (if partially successful) and then check if the atom jibo sdk node_module was really deleted.

Sorry, I don’t have precise solution.

To review, based on my past experiences…

  1. Try to install the sdk module once more…uninstall if it’s there and then close atom and be sure to check and remove the existing sdk .atom\packages\jibo-sdk. after the new install attempt, check for the red rebuild flag on the bottom right of the atom IDE and click to rebuild the sdk module.
  2. When confronted with atom/electron problems in the past on Win7, I’ve reinstalled completely. Again, remove any undeleted files under .atom/
1 Like

Hi @DunkinLee,

Thank you for providing the version numbers for those dependencies, very helpful!

As Bob (bmulreni) mentioned the SDK doesn’t support Windows 7 so there may be a limit to what can be done to get things working but I will provide as much help/input as I can.

First, I would want to know if you have or downloaded Git Shell or Git Bash. If the correct version of git isn’t present that can absolutely cause errors on install and its the reason the SDK requires those two command line tools (as opposed to the powershell tool that comes with most Windows and looks almost identical to Git Shell.) Those programs (Git Shell and Git Bash) usually come with a 2.x.x version of git. Bob mentioned he is on 2.7.0 and one of our Windows machines that I do testing on is currently at git 2.7.4.

Secondly, I noticed that you are running Visual Studio 2013. This rarely causes an issue while downloading the SDK package itself in Atom but will likely cause problems when running features like our simulator after initial install. With this in mind, you will want to download Visual Studio Community 2015. You should be able to download that long with your 2013 version if you are using that for other reasons but the Community 2015 version is specifically needed to reliably run the tool.

As a side note (because I do not believe that it is causing the error here) you will also want to make sure you match the other dependencies like itunes/bonjour listed here. Again, I do not believe it is the likely culprit here but each of those dependencies is needed to guarantee that the SDK installs/runs reliably.

If including those items (Visual Studio Community 2015 and aquiring a 2.x.x version of git by downloading Git Shell or Git Bash) do not allow the SDK package to successfully install I would suggest doing a reinstall as Bob recommends. Keep in kind that if you uninstall Atom you will also likely need to remove Visual Studio from your system. Conflicts with Atom’s installation can cause it to fail if you have Visual Studio in place at the time.

I hope this is helpful and gets things working for you :slight_smile: but, again, we can’t guarantee the tool will run/be supported on a Windows 7 machine. As a postscript, I don’t believe it has to do with your firewall because (normally) if one is on a corporate network/firewall the install error displayed looks like the one reported in this thread.