Heroku Toolbelt on Windows not installing core plugins

[ghost]

I have installed the heroku toolbelt downloaded from the website, it installs correctly, even with git and ssh. But when I try to login via CMD the output stucks in "heroku-cli: installing core plugins...", and nothing happens after several minutes or hours, when I press Ctrl+C to stop the process and try again, it says it is not supported by windows...

This is the output of the error.log

2015/11/13 09:09:12 running from C:\Users\INSPIRON 5547\AppData\Local/heroku/heroku-cli.exe
2015/11/13 09:09:12 heroku-cli: Adding dependencies...
2015/11/13 09:09:47 done
2015/11/13 09:09:47 heroku-cli: Installing core plugins...
2015/11/13 09:17:03 running from C:\Users\INSPIRON 5547\AppData\Local/heroku/heroku-cli.exe
2015/11/13 09:17:03 heroku-cli: Installing core plugins...
2015/11/13 09:17:03 not supported by windows
2015/11/13 09:17:03 not supported by windows
2015/11/13 09:17:03 not supported by windows
2015/11/13 09:17:03 not supported by windows
2015/11/13 09:17:03 not supported by windows
2015/11/13 09:17:03 not supported by windows
2015/11/13 09:17:03 not supported by windows

[ransombriggs]

What version of Windows are you running?

[ransombriggs]

Could you also open up the Windows Task Manager, go to the Processes tab and manually end the processes named heroku-cli.exe. After all of them are cleared out can you attempt running heroku login again?

[ghost]

I am Running Windows 10, I have already ended the process and start it again with no success, also deleted "heroku" folder in AppData\Local, the command install again the Toolbelt V4, then add the dependencies, but still stucks in the core plugins install process.

2015/11/13 11:29:28 running from C:\Users\INSPIRON 5547\AppData\Local/heroku/heroku-cli.exe
2015/11/13 11:29:28 heroku-cli: Adding dependencies...
2015/11/13 11:30:07 done
2015/11/13 11:30:07 heroku-cli: Installing core plugins...

after that, nothing happens.

[ransombriggs]

Could you please do me a favor and rerun the command with set GODE_DEBUG=silly set before you run the command and send us the result? This will not fix things, but should help us get more information to help debug your problem.

[ghost]

This are the last lines of the command prompt, after this nothing happens:

npm http fetch GET https://cli-npm.heroku.com/co/-/co-4.6.0.tgz
npm verb get https://cli-npm.heroku.com/strftime not expired, no request
npm verb get https://cli-npm.heroku.com/heroku-cli-util not expired, no request
npm verb get https://cli-npm.heroku.com/shell-escape not expired, no request
npm sill resolveWithNewModule filesize@3.1.3 checking installable status
npm sill cache add args [ 'filesize@3.1.3', null ]
npm verb cache add spec filesize@3.1.3
npm sill cache add parsed spec Result {
npm sill cache add raw: 'filesize@3.1.3',
npm sill cache add scope: null,
npm sill cache add name: 'filesize',
npm sill cache add rawSpec: '3.1.3',
npm sill cache add spec: '3.1.3',
npm sill cache add type: 'version' }
npm sill addNamed filesize@3.1.3
npm verb addNamed "3.1.3" is a plain semver version for filesize
npm sill mapToRegistry name filesize
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/filesize
npm verb addNameVersion registry:https://cli-npm.heroku.com/filesize not in flight; fetching
npm sill mapToRegistry name strftime
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/strftime
npm verb addRemoteTarball https://cli-npm.heroku.com/strftime/-/strftime-0.9.2.tgz not in flight; adding
npm verb addRemoteTarball [ 'https://cli-npm.heroku.com/strftime/-/strftime-0.9.2.tgz',
npm verb addRemoteTarball 'bcca2861f29456d372aaf6a17811c8bc6f39f583' ]
npm sill mapToRegistry name heroku-cli-util
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/heroku-cli-util
npm verb addRemoteTarball https://cli-npm.heroku.com/heroku-cli-util/-/heroku-cli-util-5.6.1.tgz not in flight; adding
npm verb addRemoteTarball [ 'https://cli-npm.heroku.com/heroku-cli-util/-/heroku-cli-util-5.6.1.tgz',
npm verb addRemoteTarball '15bf66dfe4d6d3360c906f4ddd94751d45b0f75b' ]
npm sill mapToRegistry name shell-escape
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/shell-escape
npm verb addRemoteTarball https://cli-npm.heroku.com/shell-escape/-/shell-escape-0.2.0.tgz not in flight; adding
npm verb addRemoteTarball [ 'https://cli-npm.heroku.com/shell-escape/-/shell-escape-0.2.0.tgz',
npm verb addRemoteTarball '68fd025eb0490b4f567a027f0bf22480b5f84133' ]
npm info retry fetch attempt 1 at 10:09:24
npm info attempt registry request try #1 at 10:09:24
npm http fetch GET https://cli-npm.heroku.com/strftime/-/strftime-0.9.2.tgz
npm sill resolveWithNewModule lodash@3.10.1 checking installable status
npm sill cache add args [ 'lodash@3.10.1', null ]
npm verb cache add spec lodash@3.10.1
npm sill cache add parsed spec Result {
npm sill cache add raw: 'lodash@3.10.1',
npm sill cache add scope: null,
npm sill cache add name: 'lodash',
npm sill cache add rawSpec: '3.10.1',
npm sill cache add spec: '3.10.1',
npm sill cache add type: 'version' }
npm sill addNamed lodash@3.10.1
npm verb addNamed "3.10.1" is a plain semver version for lodash
npm sill mapToRegistry name lodash
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/lodash
npm verb addNameVersion registry:https://cli-npm.heroku.com/lodash not in flight; fetching
npm info retry fetch attempt 1 at 10:09:24
npm info attempt registry request try #1 at 10:09:24
npm http fetch GET https://cli-npm.heroku.com/heroku-cli-util/-/heroku-cli-util-5.6.1.tgz
npm info retry fetch attempt 1 at 10:09:24
npm info attempt registry request try #1 at 10:09:24
npm http fetch GET https://cli-npm.heroku.com/shell-escape/-/shell-escape-0.2.0.tgz
npm verb get https://cli-npm.heroku.com/filesize not expired, no request
npm sill mapToRegistry name filesize
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/filesize
npm verb addRemoteTarball https://cli-npm.heroku.com/filesize/-/filesize-3.1.3.tgz not in flight; adding
npm verb addRemoteTarball [ 'https://cli-npm.heroku.com/filesize/-/filesize-3.1.3.tgz',
npm verb addRemoteTarball '50464fa77c3ef4af6e2e910cbf9b6a3da343f73a' ]
npm sill resolveWithNewModule string@3.3.1 checking installable status
npm sill cache add args [ 'string@3.3.1', null ]
npm verb cache add spec string@3.3.1
npm sill cache add parsed spec Result {
npm sill cache add raw: 'string@3.3.1',
npm sill cache add scope: null,
npm sill cache add name: 'string',
npm sill cache add rawSpec: '3.3.1',
npm sill cache add spec: '3.3.1',
npm sill cache add type: 'version' }
npm sill addNamed string@3.3.1
npm verb addNamed "3.3.1" is a plain semver version for string
npm sill mapToRegistry name string
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/string
npm verb addNameVersion registry:https://cli-npm.heroku.com/string not in flight; fetching
npm verb get https://cli-npm.heroku.com/lodash not expired, no request
npm sill mapToRegistry name lodash
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/lodash
npm verb addRemoteTarball https://cli-npm.heroku.com/lodash/-/lodash-3.10.1.tgz not in flight; adding
npm verb addRemoteTarball [ 'https://cli-npm.heroku.com/lodash/-/lodash-3.10.1.tgz',
npm verb addRemoteTarball '5bf45e8e49ba4189e17d482789dfd15bd140b7b6' ]
npm info retry fetch attempt 1 at 10:09:24
npm info attempt registry request try #1 at 10:09:24
npm http fetch GET https://cli-npm.heroku.com/filesize/-/filesize-3.1.3.tgz
npm verb get https://cli-npm.heroku.com/string not expired, no request
npm info retry fetch attempt 1 at 10:09:24
npm info attempt registry request try #1 at 10:09:24
npm http fetch GET https://cli-npm.heroku.com/lodash/-/lodash-3.10.1.tgz
npm sill mapToRegistry name string
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/string
npm verb addRemoteTarball https://cli-npm.heroku.com/string/-/string-3.3.1.tgz not in flight; adding
npm verb addRemoteTarball [ 'https://cli-npm.heroku.com/string/-/string-3.3.1.tgz',
npm verb addRemoteTarball '8d2757ec1c0e6c526796fbb6b14036a4098398b7' ]
npm info retry fetch attempt 1 at 10:09:24
npm info attempt registry request try #1 at 10:09:24
npm http fetch GET https://cli-npm.heroku.com/string/-/string-3.3.1.tgz
npm http fetch 200 https://cli-npm.heroku.com/co/-/co-4.6.0.tgz
npm sill fetchAndShaCheck shasum 6ea6bdf3d853ae54ccb8e47bfa0bf3f9031fb184
npm verb addTmpTarball C:\Users\INSPIR1\AppData\Local\Temp\npm-17056-a29eea20\cli-npm.heroku.com\co-\co-4.6.0.tgz not in flight; adding
npm verb addTmpTarball already have metadata; skipping unpack for co@4.6.0
npm sill cache afterAdd co@4.6.0
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\co\4.6.0\package\package.json not in flight; writing
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\co\4.6.0\package\package.json written
npm http fetch 200 https://cli-npm.heroku.com/shell-escape/-/shell-escape-0.2.0.tgz
npm http fetch 200 https://cli-npm.heroku.com/heroku-cli-util/-/heroku-cli-util-5.6.1.tgz
npm sill fetchAndShaCheck shasum 68fd025eb0490b4f567a027f0bf22480b5f84133
npm verb addTmpTarball C:\Users\INSPIR1\AppData\Local\Temp\npm-17056-a29eea20\cli-npm.heroku.com\shell-escape-\shell-escape-0.2.0.tgz not in flight; adding
npm verb addTmpTarball already have metadata; skipping unpack for shell-escape@0.2.0
npm sill cache afterAdd shell-escape@0.2.0
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\shell-escape\0.2.0\package\package.json not in flight; writing
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\shell-escape\0.2.0\package\package.json written
npm http fetch 200 https://cli-npm.heroku.com/strftime/-/strftime-0.9.2.tgz
npm sill fetchAndShaCheck shasum bcca2861f29456d372aaf6a17811c8bc6f39f583
npm verb addTmpTarball C:\Users\INSPIR1\AppData\Local\Temp\npm-17056-a29eea20\cli-npm.heroku.com\strftime-\strftime-0.9.2.tgz not in flight; adding
npm verb addTmpTarball already have metadata; skipping unpack for strftime@0.9.2
npm http fetch 200 https://cli-npm.heroku.com/filesize/-/filesize-3.1.3.tgz
npm sill fetchAndShaCheck shasum 50464fa77c3ef4af6e2e910cbf9b6a3da343f73a
npm sill fetchAndShaCheck shasum 15bf66dfe4d6d3360c906f4ddd94751d45b0f75b
npm verb addTmpTarball C:\Users\INSPIR1\AppData\Local\Temp\npm-17056-a29eea20\cli-npm.heroku.com\filesize-\filesize-3.1.3.tgz not in flight; adding
npm verb addTmpTarball already have metadata; skipping unpack for filesize@3.1.3
npm verb addTmpTarball C:\Users\INSPIR1\AppData\Local\Temp\npm-17056-a29eea20\cli-npm.heroku.com\heroku-cli-util-\heroku-cli-util-5.6.1.tgz not in flight; adding
npm verb addTmpTarball already have metadata; skipping unpack for heroku-cli-util@5.6.1
npm sill cache afterAdd strftime@0.9.2
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\strftime\0.9.2\package\package.json not in flight; writing
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\strftime\0.9.2\package\package.json written
npm sill cache afterAdd heroku-cli-util@5.6.1
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\heroku-cli-util\5.6.1\package\package.json not in flight; writing
npm sill cache afterAdd filesize@3.1.3
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\filesize\3.1.3\package\package.json not in flight; writing
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\heroku-cli-util\5.6.1\package\package.json written
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\filesize\3.1.3\package\package.json written
npm http fetch 200 https://cli-npm.heroku.com/string/-/string-3.3.1.tgz
npm http fetch 200 https://cli-npm.heroku.com/lodash/-/lodash-3.10.1.tgz
npm sill fetchAndShaCheck shasum 8d2757ec1c0e6c526796fbb6b14036a4098398b7
npm verb addTmpTarball C:\Users\INSPIR1\AppData\Local\Temp\npm-17056-a29eea20\cli-npm.heroku.com\string-\string-3.3.1.tgz not in flight; adding
npm verb addTmpTarball already have metadata; skipping unpack for string@3.3.1
npm sill cache afterAdd string@3.3.1
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\string\3.3.1\package\package.json not in flight; writing
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\string\3.3.1\package\package.json written
npm sill fetchAndShaCheck shasum 5bf45e8e49ba4189e17d482789dfd15bd140b7b6
npm verb addTmpTarball C:\Users\INSPIR1\AppData\Local\Temp\npm-17056-a29eea20\cli-npm.heroku.com\lodash-\lodash-3.10.1.tgz not in flight; adding
npm verb addTmpTarball already have metadata; skipping unpack for lodash@3.10.1
npm sill cache afterAdd lodash@3.10.1
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\lodash\3.10.1\package\package.json not in flight; writing
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\lodash\3.10.1\package\package.json written
npm sill fetchNamedPackageData chalk
npm sill mapToRegistry name chalk
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/chalk
npm sill fetchNamedPackageData heroku-client
npm sill mapToRegistry name heroku-client
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/heroku-client
npm verb request uri https://cli-npm.heroku.com/chalk
npm verb request no auth needed
npm info attempt registry request try #1 at 10:09:25
npm http request GET https://cli-npm.heroku.com/chalk
npm verb request uri https://cli-npm.heroku.com/heroku-client
npm verb request no auth needed
npm info attempt registry request try #1 at 10:09:25
npm http request GET https://cli-npm.heroku.com/heroku-client
npm http 200 https://cli-npm.heroku.com/chalk
npm verb headers { 'content-type': 'application/json; charset=utf-8',
npm verb headers 'content-length': '6757',
npm verb headers connection: 'keep-alive',
npm verb headers server: 'Cowboy',
npm verb headers etag: '"C9YD3V5XE0DT3DYNQ0TDN3KVX"',
npm verb headers 'cache-control': 'public, max-age=200',
npm verb headers 'content-encoding': 'gzip',
npm verb headers date: 'Tue, 17 Nov 2015 15:58:58 GMT',
npm verb headers via: '1.1 vegur, 1.1 c23c9393a7f4dd8628e92239da722716.cloudfront.net (CloudFront)',
npm verb headers 'x-cache': 'RefreshHit from cloudfront',
npm verb headers 'x-amz-cf-id': 'TcuA4nbvjtaaSMwMA4HqV9H8R0kL4miuhpR54DFcHKgfPh5IticPBQ==' }
npm sill get cb [ 200,
npm sill get { 'content-type': 'application/json; charset=utf-8',
npm sill get 'content-length': '6757',
npm sill get connection: 'keep-alive',
npm sill get server: 'Cowboy',
npm sill get etag: '"C9YD3V5XE0DT3DYNQ0TDN3KVX"',
npm sill get 'cache-control': 'public, max-age=200',
npm sill get 'content-encoding': 'gzip',
npm sill get date: 'Tue, 17 Nov 2015 15:58:58 GMT',
npm sill get via: '1.1 vegur, 1.1 c23c9393a7f4dd8628e92239da722716.cloudfront.net (CloudFront)',
npm sill get 'x-cache': 'RefreshHit from cloudfront',
npm sill get 'x-amz-cf-id': 'TcuA4nbvjtaaSMwMA4HqV9H8R0kL4miuhpR54DFcHKgfPh5IticPBQ==' } ]
npm verb get saving chalk to C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\cli-npm.heroku.com\chalk.cache.json
npm http 200 https://cli-npm.heroku.com/heroku-client
npm verb headers { 'content-type': 'application/json; charset=utf-8',
npm verb headers 'content-length': '8583',
npm verb headers connection: 'keep-alive',
npm verb headers server: 'Cowboy',
npm verb headers etag: '"1VU6C8CAOUWJI9S9PH78ZHCKR"',
npm verb headers 'cache-control': 'public, max-age=200',
npm verb headers 'content-encoding': 'gzip',
npm verb headers date: 'Tue, 17 Nov 2015 16:05:35 GMT',
npm verb headers via: '1.1 vegur, 1.1 19248db84f8828dab6092e0e9988f5a0.cloudfront.net (CloudFront)',
npm verb headers 'x-cache': 'RefreshHit from cloudfront',
npm verb headers 'x-amz-cf-id': 'jm85bg73-C5oljjdIIsCXVBhaxHfQOQyNMdlP6FRkoo1zaMmQKyWjQ==' }
npm sill get cb [ 200,
npm sill get { 'content-type': 'application/json; charset=utf-8',
npm sill get 'content-length': '8583',
npm sill get connection: 'keep-alive',
npm sill get server: 'Cowboy',
npm sill get etag: '"1VU6C8CAOUWJI9S9PH78ZHCKR"',
npm sill get 'cache-control': 'public, max-age=200',
npm sill get 'content-encoding': 'gzip',
npm sill get date: 'Tue, 17 Nov 2015 16:05:35 GMT',
npm sill get via: '1.1 vegur, 1.1 19248db84f8828dab6092e0e9988f5a0.cloudfront.net (CloudFront)',
npm sill get 'x-cache': 'RefreshHit from cloudfront',
npm sill get 'x-amz-cf-id': 'jm85bg73-C5oljjdIIsCXVBhaxHfQOQyNMdlP6FRkoo1zaMmQKyWjQ==' } ]
npm verb get saving heroku-client to C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\cli-npm.heroku.com\heroku-client.cache.json
npm sill resolveWithNewModule chalk@1.1.1 checking installable status
npm sill cache add args [ 'chalk@1.1.1', null ]
npm verb cache add spec chalk@1.1.1
npm sill cache add parsed spec Result {
npm sill cache add raw: 'chalk@1.1.1',
npm sill cache add scope: null,
npm sill cache add name: 'chalk',
npm sill cache add rawSpec: '1.1.1',
npm sill cache add spec: '1.1.1',
npm sill cache add type: 'version' }
npm sill addNamed chalk@1.1.1
npm verb addNamed "1.1.1" is a plain semver version for chalk
npm sill mapToRegistry name chalk
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/chalk
npm verb addNameVersion registry:https://cli-npm.heroku.com/chalk not in flight; fetching
npm verb get https://cli-npm.heroku.com/chalk not expired, no request
npm sill mapToRegistry name chalk
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/chalk
npm verb addRemoteTarball https://cli-npm.heroku.com/chalk/-/chalk-1.1.1.tgz not in flight; adding
npm verb addRemoteTarball [ 'https://cli-npm.heroku.com/chalk/-/chalk-1.1.1.tgz',
npm verb addRemoteTarball '509afb67066e7499f7eb3535c77445772ae2d019' ]
npm info retry fetch attempt 1 at 10:09:25
npm info attempt registry request try #1 at 10:09:25
npm http fetch GET https://cli-npm.heroku.com/chalk/-/chalk-1.1.1.tgz
npm sill resolveWithNewModule heroku-client@2.3.2 checking installable status
npm sill cache add args [ 'heroku-client@2.3.2', null ]
npm verb cache add spec heroku-client@2.3.2
npm sill cache add parsed spec Result {
npm sill cache add raw: 'heroku-client@2.3.2',
npm sill cache add scope: null,
npm sill cache add name: 'heroku-client',
npm sill cache add rawSpec: '2.3.2',
npm sill cache add spec: '2.3.2',
npm sill cache add type: 'version' }
npm sill addNamed heroku-client@2.3.2
npm verb addNamed "2.3.2" is a plain semver version for heroku-client
npm sill mapToRegistry name heroku-client
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/heroku-client
npm verb addNameVersion registry:https://cli-npm.heroku.com/heroku-client not in flight; fetching
npm verb get https://cli-npm.heroku.com/heroku-client not expired, no request
npm sill mapToRegistry name heroku-client
npm sill mapToRegistry using default registry
npm sill mapToRegistry registry https://cli-npm.heroku.com/
npm sill mapToRegistry uri https://cli-npm.heroku.com/heroku-client
npm verb addRemoteTarball https://cli-npm.heroku.com/heroku-client/-/heroku-client-2.3.2.tgz not in flight; adding
npm verb addRemoteTarball [ 'https://cli-npm.heroku.com/heroku-client/-/heroku-client-2.3.2.tgz',
npm verb addRemoteTarball 'a74e4acfa0db16aae740b78f574b6eb974ffbe6e' ]
npm info retry fetch attempt 1 at 10:09:25
npm info attempt registry request try #1 at 10:09:25
npm http fetch GET https://cli-npm.heroku.com/heroku-client/-/heroku-client-2.3.2.tgz
npm http fetch 200 https://cli-npm.heroku.com/chalk/-/chalk-1.1.1.tgz
npm sill fetchAndShaCheck shasum 509afb67066e7499f7eb3535c77445772ae2d019
npm verb addTmpTarball C:\Users\INSPIR1\AppData\Local\Temp\npm-17056-a29eea20\cli-npm.heroku.com\chalk-\chalk-1.1.1.tgz not in flight; adding
npm verb addTmpTarball already have metadata; skipping unpack for chalk@1.1.1
npm sill cache afterAdd chalk@1.1.1
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\chalk\1.1.1\package\package.json not in flight; writing
npm verb afterAdd C:\Users\INSPIRON 5547\AppData\Local\heroku.npm-cache\chalk\1.1.1\package\package.json written

[ghost]

I found that running "heroku" command many times, the output changed every time, sometimes it stucked in one line, then every time stucked in different line, so I ran it many times until "ok" was shown... then everything was fine.

[ransombriggs]

Thanks a lot for your help in debugging this, it has given me an idea what direction to look.

[leonkidd]

Hi @ransombriggs , I have the same problem, could you please help me to fix it.

[ransombriggs]

@leonkidd Could you please set GODE_DEBUG=info and set HEROKU_DEBUG=1 and paste your output?

[leonkidd]

@ransombriggs Thanks.
npm info ok
npm info it worked if it ends with ok
npm info using npm@3.3.10
npm info using node@v5.7.1
npm info lifecycle wrappy@1.0.1preuninstall: wrappy@1.0.1
npm info lifecycle wrappy@1.0.1uninstall: wrappy@1.0.1
npm info lifecycle wrappy@1.0.1postuninstall: wrappy@1.0.1
npm info lifecycle validator@4.8.0preuninstall: validator@4.8.0
npm info lifecycle validator@4.8.0uninstall: validator@4.8.0
npm info lifecycle validator@4.8.0postuninstall: validator@4.8.0
npm info lifecycle url-parse-lax@1.0.0preuninstall: url-parse-lax@1.0.0
npm info lifecycle url-parse-lax@1.0.0uninstall: url-parse-lax@1.0.0
npm info lifecycle url-parse-lax@1.0.0postuninstall: url-parse-lax@1.0.0
npm info lifecycle unzip-response@1.0.0preuninstall: unzip-response@1.0.0
npm info lifecycle unzip-response@1.0.0uninstall: unzip-response@1.0.0
npm info lifecycle unzip-response@1.0.0postuninstall: unzip-response@1.0.0
npm info lifecycle tunnel-agent@0.4.2preuninstall: tunnel-agent@0.4.2
npm info lifecycle tunnel-agent@0.4.2uninstall: tunnel-agent@0.4.2
npm info lifecycle tunnel-agent@0.4.2postuninstall: tunnel-agent@0.4.2
npm info lifecycle timed-out@2.0.0preuninstall: timed-out@2.0.0
npm info lifecycle timed-out@2.0.0uninstall: timed-out@2.0.0
npm info lifecycle timed-out@2.0.0postuninstall: timed-out@2.0.0
npm info lifecycle through@2.3.8preuninstall: through@2.3.8
npm info lifecycle through@2.3.8uninstall: through@2.3.8
npm info lifecycle through@2.3.8postuninstall: through@2.3.8
npm info lifecycle supports-color@2.0.0preuninstall: supports-color@2.0.0
npm info lifecycle supports-color@2.0.0uninstall: supports-color@2.0.0
npm info lifecycle supports-color@2.0.0postuninstall: supports-color@2.0.0
npm info lifecycle strip-ansi@3.0.1preuninstall: strip-ansi@3.0.1
npm info lifecycle strip-ansi@3.0.1uninstall: strip-ansi@3.0.1
npm info lifecycle strip-ansi@3.0.1postuninstall: strip-ansi@3.0.1
npm info lifecycle string-width@1.0.1preuninstall: string-width@1.0.1
npm info lifecycle string-width@1.0.1uninstall: string-width@1.0.1
npm info lifecycle string-width@1.0.1postuninstall: string-width@1.0.1
npm info lifecycle string-just@0.0.2preuninstall: string-just@0.0.2
npm info lifecycle string-just@0.0.2uninstall: string-just@0.0.2
npm info lifecycle string-just@0.0.2postuninstall: string-just@0.0.2
npm info lifecycle string@3.3.1preuninstall: string@3.3.1
npm info lifecycle string@3.3.1uninstall: string@3.3.1
npm info lifecycle string@3.3.1postuninstall: string@3.3.1
npm info lifecycle strftime@0.9.2preuninstall: strftime@0.9.2
npm info lifecycle strftime@0.9.2uninstall: strftime@0.9.2
npm info lifecycle strftime@0.9.2postuninstall: strftime@0.9.2
npm info lifecycle shell-escape@0.2.0preuninstall: shell-escape@0.2.0
npm info lifecycle shell-escape@0.2.0uninstall: shell-escape@0.2.0
npm info lifecycle shell-escape@0.2.0postuninstall: shell-escape@0.2.0
npm info lifecycle rx-lite@3.1.2preuninstall: rx-lite@3.1.2
npm info lifecycle rx-lite@3.1.2uninstall: rx-lite@3.1.2
npm info lifecycle rx-lite@3.1.2postuninstall: rx-lite@3.1.2
npm info lifecycle run-async@0.1.0preuninstall: run-async@0.1.0
npm info lifecycle run-async@0.1.0uninstall: run-async@0.1.0
npm info lifecycle run-async@0.1.0postuninstall: run-async@0.1.0
npm info lifecycle restore-cursor@1.0.1preuninstall: restore-cursor@1.0.1
npm info lifecycle restore-cursor@1.0.1uninstall: restore-cursor@1.0.1
npm info lifecycle restore-cursor@1.0.1postuninstall: restore-cursor@1.0.1
npm info lifecycle readline2@1.0.1preuninstall: readline2@1.0.1
npm info lifecycle readline2@1.0.1uninstall: readline2@1.0.1
npm info lifecycle readline2@1.0.1postuninstall: readline2@1.0.1
npm info lifecycle q@1.4.1preuninstall: q@1.4.1
npm info lifecycle q@1.4.1uninstall: q@1.4.1
npm info lifecycle q@1.4.1postuninstall: q@1.4.1
npm info lifecycle printf@0.2.3preuninstall: printf@0.2.3
npm info lifecycle printf@0.2.3uninstall: printf@0.2.3
npm info lifecycle printf@0.2.3postuninstall: printf@0.2.3
npm info lifecycle prepend-http@1.0.3preuninstall: prepend-http@1.0.3
npm info lifecycle prepend-http@1.0.3uninstall: prepend-http@1.0.3
npm info lifecycle prepend-http@1.0.3postuninstall: prepend-http@1.0.3
npm info lifecycle inflection@1.3.8preuninstall: inflection@1.3.8
npm info lifecycle inflection@1.3.8uninstall: inflection@1.3.8
npm info lifecycle inflection@1.3.8postuninstall: inflection@1.3.8
npm info lifecycle path-proxy@1.0.0preuninstall: path-proxy@1.0.0
npm info lifecycle path-proxy@1.0.0uninstall: path-proxy@1.0.0
npm info lifecycle path-proxy@1.0.0postuninstall: path-proxy@1.0.0
npm info lifecycle opn@3.0.3preuninstall: opn@3.0.3
npm info lifecycle opn@3.0.3uninstall: opn@3.0.3
npm info lifecycle opn@3.0.3postuninstall: opn@3.0.3
npm info lifecycle onetime@1.1.0preuninstall: onetime@1.1.0
npm info lifecycle onetime@1.1.0uninstall: onetime@1.1.0
npm info lifecycle onetime@1.1.0postuninstall: onetime@1.1.0
npm info lifecycle once@1.3.3preuninstall: once@1.3.3
npm info lifecycle once@1.3.3uninstall: once@1.3.3
npm info lifecycle once@1.3.3postuninstall: once@1.3.3
npm info lifecycle object-assign@4.0.1preuninstall: object-assign@4.0.1
npm info lifecycle object-assign@4.0.1uninstall: object-assign@4.0.1
npm info lifecycle object-assign@4.0.1postuninstall: object-assign@4.0.1
npm info lifecycle number-is-nan@1.0.0preuninstall: number-is-nan@1.0.0
npm info lifecycle number-is-nan@1.0.0uninstall: number-is-nan@1.0.0
npm info lifecycle number-is-nan@1.0.0postuninstall: number-is-nan@1.0.0
npm info lifecycle node-status-codes@2.0.0~preuninstall: node-status-codes@2.0.0

npm info lifecycle node-status-codes@2.0.0uninstall: node-status-codes@2.0.0
npm info lifecycle node-status-codes@2.0.0postuninstall: node-status-codes@2.0.
0
npm info lifecycle mute-stream@0.0.5preuninstall: mute-stream@0.0.5
npm info lifecycle mute-stream@0.0.5uninstall: mute-stream@0.0.5
npm info lifecycle mute-stream@0.0.5postuninstall: mute-stream@0.0.5
npm info lifecycle moment@2.11.1preuninstall: moment@2.11.1
npm info lifecycle moment@2.11.1uninstall: moment@2.11.1
npm info lifecycle moment@2.11.1postuninstall: moment@2.11.1
npm info lifecycle lowercase-keys@1.0.0preuninstall: lowercase-keys@1.0.0
npm info lifecycle lowercase-keys@1.0.0uninstall: lowercase-keys@1.0.0
npm info lifecycle lowercase-keys@1.0.0postuninstall: lowercase-keys@1.0.0
npm info lifecycle lodash@4.0.1preuninstall: lodash@4.0.1
npm info lifecycle lodash@4.0.1uninstall: lodash@4.0.1
npm info lifecycle lodash@4.0.1postuninstall: lodash@4.0.1
npm info lifecycle is-stream@1.0.1preuninstall: is-stream@1.0.1
npm info lifecycle is-stream@1.0.1uninstall: is-stream@1.0.1
npm info lifecycle is-stream@1.0.1postuninstall: is-stream@1.0.1
npm info lifecycle is-retry-allowed@1.0.0preuninstall: is-retry-allowed@1.0.0
npm info lifecycle is-retry-allowed@1.0.0uninstall: is-retry-allowed@1.0.0
npm info lifecycle is-retry-allowed@1.0.0postuninstall: is-retry-allowed@1.0.0
npm info lifecycle is-redirect@1.0.0preuninstall: is-redirect@1.0.0
npm info lifecycle is-redirect@1.0.0uninstall: is-redirect@1.0.0
npm info lifecycle is-redirect@1.0.0postuninstall: is-redirect@1.0.0
npm info lifecycle is-plain-obj@1.1.0preuninstall: is-plain-obj@1.1.0
npm info lifecycle is-plain-obj@1.1.0uninstall: is-plain-obj@1.1.0
npm info lifecycle is-plain-obj@1.1.0postuninstall: is-plain-obj@1.1.0
npm info lifecycle is-fullwidth-code-point@1.0.0preuninstall: is-fullwidth-code
-point@1.0.0
npm info lifecycle is-fullwidth-code-point@1.0.0uninstall: is-fullwidth-code-po
int@1.0.0
npm info lifecycle is-fullwidth-code-point@1.0.0postuninstall: is-fullwidth-cod
e-point@1.0.0
npm info lifecycle lodash@4.6.1preuninstall: lodash@4.6.1
npm info lifecycle lodash@4.6.1uninstall: lodash@4.6.1
npm info lifecycle lodash@4.6.1postuninstall: lodash@4.6.1
npm info lifecycle inquirer@0.12.0preuninstall: inquirer@0.12.0
npm info lifecycle inquirer@0.12.0uninstall: inquirer@0.12.0
npm info lifecycle inquirer@0.12.0postuninstall: inquirer@0.12.0
npm info lifecycle inflection@1.8.0preuninstall: inflection@1.8.0
npm info lifecycle inflection@1.8.0uninstall: inflection@1.8.0
npm info lifecycle inflection@1.8.0postuninstall: inflection@1.8.0
npm info lifecycle heroku-status@2.1.0preuninstall: heroku-status@2.1.0
npm info lifecycle heroku-status@2.1.0uninstall: heroku-status@2.1.0
npm info lifecycle heroku-status@2.1.0postuninstall: heroku-status@2.1.0
npm info lifecycle heroku-spaces@2.0.14preuninstall: heroku-spaces@2.0.14
npm info lifecycle heroku-spaces@2.0.14uninstall: heroku-spaces@2.0.14
npm info lifecycle heroku-spaces@2.0.14postuninstall: heroku-spaces@2.0.14
npm info lifecycle heroku-run@2.9.2preuninstall: heroku-run@2.9.2
npm info lifecycle heroku-run@2.9.2uninstall: heroku-run@2.9.2
npm info lifecycle heroku-run@2.9.2postuninstall: heroku-run@2.9.2
npm info lifecycle heroku-pipelines@1.1.1preuninstall: heroku-pipelines@1.1.1
npm info lifecycle heroku-pipelines@1.1.1uninstall: heroku-pipelines@1.1.1
npm info lifecycle heroku-pipelines@1.1.1postuninstall: heroku-pipelines@1.1.1
npm info lifecycle heroku-orgs@1.0.4preuninstall: heroku-orgs@1.0.4
npm info lifecycle heroku-orgs@1.0.4uninstall: heroku-orgs@1.0.4
npm info lifecycle heroku-orgs@1.0.4postuninstall: heroku-orgs@1.0.4
npm info lifecycle heroku-local@4.1.7preuninstall: heroku-local@4.1.7
npm info lifecycle heroku-local@4.1.7uninstall: heroku-local@4.1.7
npm info lifecycle heroku-local@4.1.7postuninstall: heroku-local@4.1.7
npm info lifecycle heroku-git@2.4.5preuninstall: heroku-git@2.4.5
npm info lifecycle heroku-git@2.4.5uninstall: heroku-git@2.4.5
npm info lifecycle heroku-git@2.4.5postuninstall: heroku-git@2.4.5
npm info lifecycle heroku-fork@4.1.1preuninstall: heroku-fork@4.1.1
npm info lifecycle heroku-fork@4.1.1uninstall: heroku-fork@4.1.1
npm info lifecycle heroku-fork@4.1.1postuninstall: heroku-fork@4.1.1
npm info lifecycle heroku-client@2.4.0preuninstall: heroku-client@2.4.0
npm info lifecycle heroku-client@2.4.0uninstall: heroku-client@2.4.0
npm info lifecycle heroku-client@2.4.0postuninstall: heroku-client@2.4.0
npm info lifecycle heroku-cli-util@5.7.4preuninstall: heroku-cli-util@5.7.4
npm info lifecycle heroku-cli-util@5.7.4uninstall: heroku-cli-util@5.7.4
npm info lifecycle heroku-cli-util@5.7.4postuninstall: heroku-cli-util@5.7.4
npm info lifecycle heroku-cli-addons@0.2.1~preuninstall: heroku-cli-addons@0.2.1

npm info lifecycle heroku-cli-addons@0.2.1uninstall: heroku-cli-addons@0.2.1
npm info lifecycle heroku-cli-addons@0.2.1postuninstall: heroku-cli-addons@0.2.
1
npm info lifecycle heroku-apps@1.2.5preuninstall: heroku-apps@1.2.5
npm info lifecycle heroku-apps@1.2.5uninstall: heroku-apps@1.2.5
npm info lifecycle heroku-apps@1.2.5postuninstall: heroku-apps@1.2.5
npm info lifecycle has-ansi@2.0.0preuninstall: has-ansi@2.0.0
npm info lifecycle has-ansi@2.0.0uninstall: has-ansi@2.0.0
npm info lifecycle has-ansi@2.0.0postuninstall: has-ansi@2.0.0
npm info lifecycle got@6.1.1preuninstall: got@6.1.1
npm info lifecycle got@6.1.1uninstall: got@6.1.1
npm info lifecycle got@6.1.1postuninstall: got@6.1.1
npm info lifecycle get-stream@1.1.0preuninstall: get-stream@1.1.0
npm info lifecycle get-stream@1.1.0uninstall: get-stream@1.1.0
npm info lifecycle get-stream@1.1.0postuninstall: get-stream@1.1.0
npm info lifecycle filesize@3.2.0preuninstall: filesize@3.2.0
npm info lifecycle filesize@3.2.0uninstall: filesize@3.2.0
npm info lifecycle filesize@3.2.0postuninstall: filesize@3.2.0
npm info lifecycle figures@1.4.0preuninstall: figures@1.4.0
npm info lifecycle figures@1.4.0uninstall: figures@1.4.0
npm info lifecycle figures@1.4.0postuninstall: figures@1.4.0
npm info lifecycle exit-hook@1.1.1preuninstall: exit-hook@1.1.1
npm info lifecycle exit-hook@1.1.1uninstall: exit-hook@1.1.1
npm info lifecycle exit-hook@1.1.1postuninstall: exit-hook@1.1.1
npm info lifecycle escape-string-regexp@1.0.5preuninstall: escape-string-regexp
@1.0.5
npm info lifecycle escape-string-regexp@1.0.5uninstall: escape-string-regexp@1.
0.5
npm info lifecycle escape-string-regexp@1.0.5postuninstall: escape-string-regex
p@1.0.5
npm info lifecycle duplexer3@0.1.4preuninstall: duplexer3@0.1.4
npm info lifecycle duplexer3@0.1.4uninstall: duplexer3@0.1.4
npm info lifecycle duplexer3@0.1.4postuninstall: duplexer3@0.1.4
npm info lifecycle depd@1.1.0preuninstall: depd@1.1.0
npm info lifecycle depd@1.1.0uninstall: depd@1.1.0
npm info lifecycle depd@1.1.0postuninstall: depd@1.1.0
npm info lifecycle create-error-class@3.0.1preuninstall: create-error-class@3.0
.1
npm info lifecycle create-error-class@3.0.1uninstall: create-error-class@3.0.1
npm info lifecycle create-error-class@3.0.1postuninstall: create-error-class@3.
0.1
npm info lifecycle color-convert@1.0.0preuninstall: color-convert@1.0.0
npm info lifecycle color-convert@1.0.0uninstall: color-convert@1.0.0
npm info lifecycle color-convert@1.0.0postuninstall: color-convert@1.0.0
npm info lifecycle code-point-at@1.0.0preuninstall: code-point-at@1.0.0
npm info lifecycle code-point-at@1.0.0uninstall: code-point-at@1.0.0
npm info lifecycle code-point-at@1.0.0postuninstall: code-point-at@1.0.0
npm info lifecycle co@4.6.0preuninstall: co@4.6.0
npm info lifecycle co@4.6.0uninstall: co@4.6.0
npm info lifecycle co@4.6.0postuninstall: co@4.6.0
npm info lifecycle cli-width@2.1.0preuninstall: cli-width@2.1.0
npm info lifecycle cli-width@2.1.0uninstall: cli-width@2.1.0
npm info lifecycle cli-width@2.1.0postuninstall: cli-width@2.1.0
npm info lifecycle cli-cursor@1.0.2preuninstall: cli-cursor@1.0.2
npm info lifecycle cli-cursor@1.0.2uninstall: cli-cursor@1.0.2
npm info lifecycle cli-cursor@1.0.2postuninstall: cli-cursor@1.0.2
npm info lifecycle chalk@1.1.1preuninstall: chalk@1.1.1
npm info lifecycle chalk@1.1.1uninstall: chalk@1.1.1
npm info lifecycle chalk@1.1.1postuninstall: chalk@1.1.1
npm info lifecycle capture-stack-trace@1.0.0preuninstall: capture-stack-trace@1
.0.0
npm info lifecycle capture-stack-trace@1.0.0uninstall: capture-stack-trace@1.0.
0
npm info lifecycle capture-stack-trace@1.0.0postuninstall: capture-stack-trace@
1.0.0
npm info lifecycle bluebird-queue@0.0.8preuninstall: bluebird-queue@0.0.8
npm info lifecycle bluebird-queue@0.0.8uninstall: bluebird-queue@0.0.8
npm info lifecycle bluebird-queue@0.0.8postuninstall: bluebird-queue@0.0.8
npm info lifecycle bluebird@2.10.2preuninstall: bluebird@2.10.2
npm info lifecycle bluebird@2.10.2uninstall: bluebird@2.10.2
npm info lifecycle bluebird@2.10.2postuninstall: bluebird@2.10.2
npm info lifecycle ansi-styles@2.2.0preuninstall: ansi-styles@2.2.0
npm info lifecycle ansi-styles@2.2.0uninstall: ansi-styles@2.2.0
npm info lifecycle ansi-styles@2.2.0postuninstall: ansi-styles@2.2.0
npm info lifecycle ansi-regex@2.0.0preuninstall: ansi-regex@2.0.0
npm info lifecycle ansi-regex@2.0.0uninstall: ansi-regex@2.0.0
npm info lifecycle ansi-regex@2.0.0postuninstall: ansi-regex@2.0.0
npm info lifecycle ansi-escapes@1.3.0preuninstall: ansi-escapes@1.3.0
npm info lifecycle ansi-escapes@1.3.0uninstall: ansi-escapes@1.3.0
npm info lifecycle ansi-escapes@1.3.0postuninstall: ansi-escapes@1.3.0
npm info lifecycle heroku-cli-util@5.7.3preuninstall: heroku-cli-util@5.7.3
npm info lifecycle heroku-cli-util@5.7.3uninstall: heroku-cli-util@5.7.3
npm info lifecycle heroku-cli-util@5.7.3postuninstall: heroku-cli-util@5.7.3
npm info lifecycle lodash@3.10.1preuninstall: lodash@3.10.1
npm info lifecycle lodash@3.10.1uninstall: lodash@3.10.1
npm info lifecycle lodash@3.10.1postuninstall: lodash@3.10.1
npm info lifecycle heroku-cli-util@5.6.3preuninstall: heroku-cli-util@5.6.3
npm info lifecycle heroku-cli-util@5.6.3uninstall: heroku-cli-util@5.6.3
npm info lifecycle heroku-cli-util@5.6.3postuninstall: heroku-cli-util@5.6.3
npm info lifecycle lodash@3.10.1preuninstall: lodash@3.10.1
npm info lifecycle lodash@3.10.1uninstall: lodash@3.10.1
npm info lifecycle lodash@3.10.1postuninstall: lodash@3.10.1
npm info lifecycle heroku-cli-util@5.8.0preuninstall: heroku-cli-util@5.8.0
npm info lifecycle heroku-cli-util@5.8.0uninstall: heroku-cli-util@5.8.0
npm info lifecycle heroku-cli-util@5.8.0postuninstall: heroku-cli-util@5.8.0
npm info lifecycle heroku-cli-util@5.8.0preuninstall: heroku-cli-util@5.8.0
npm info lifecycle heroku-cli-util@5.8.0uninstall: heroku-cli-util@5.8.0
npm info lifecycle heroku-cli-util@5.8.0postuninstall: heroku-cli-util@5.8.0
npm info lifecycle heroku-cli-util@5.7.3preuninstall: heroku-cli-util@5.7.3
npm info lifecycle heroku-cli-util@5.7.3uninstall: heroku-cli-util@5.7.3
npm info lifecycle heroku-cli-util@5.7.3postuninstall: heroku-cli-util@5.7.3
npm info lifecycle lodash@3.10.1preuninstall: lodash@3.10.1
npm info lifecycle lodash@3.10.1uninstall: lodash@3.10.1
npm info lifecycle lodash@3.10.1~postuninstall: lodash@3.10.1
npm WARN ENOENT ENOENT: no such file or directory, open 'C:\Users\Leon\AppData\L
ocal\heroku\package.json'
npm WARN EPACKAGEJSON heroku No description
npm WARN EPACKAGEJSON heroku No repository field.
npm WARN EPACKAGEJSON heroku No README data
npm WARN EPACKAGEJSON heroku No license field.

[leonkidd]

@ransombriggs after i removing the files of %AppDate%/local/heroku and trying again, These show up:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Users\Leon\AppData\Local\heroku\node-v5.7.1-windows-x86\bin\node.exe',
1 verbose cli 'C:\Users\Leon\AppData\Local\heroku\node-v5.7.1-windows-x86\lib\node_modules\npm\cli.js',
1 verbose cli 'install',
1 verbose cli 'heroku-apps',
1 verbose cli 'heroku-cli-addons',
1 verbose cli 'heroku-fork',
1 verbose cli 'heroku-git',
1 verbose cli 'heroku-local',
1 verbose cli 'heroku-orgs',
1 verbose cli 'heroku-pipelines',
1 verbose cli 'heroku-run',
1 verbose cli 'heroku-spaces',
1 verbose cli 'heroku-status' ]
2 info using npm@3.3.10
3 info using node@v5.7.1
4 silly loadCurrentTree Starting
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly fetchPackageMetaData heroku-apps
8 silly fetchPackageMetaData heroku-cli-addons
9 silly fetchPackageMetaData heroku-fork
10 silly fetchPackageMetaData heroku-git
11 silly fetchPackageMetaData heroku-local
12 silly fetchPackageMetaData heroku-orgs
13 silly fetchPackageMetaData heroku-pipelines
14 silly fetchPackageMetaData heroku-run
15 silly fetchPackageMetaData heroku-spaces
16 silly fetchPackageMetaData heroku-status
17 silly fetchNamedPackageData heroku-apps
18 silly mapToRegistry name heroku-apps
19 silly mapToRegistry using default registry
20 silly mapToRegistry registry https://cli-npm.heroku.com/
21 silly mapToRegistry uri https://cli-npm.heroku.com/heroku-apps
22 silly fetchNamedPackageData heroku-cli-addons
23 silly mapToRegistry name heroku-cli-addons
24 silly mapToRegistry using default registry
25 silly mapToRegistry registry https://cli-npm.heroku.com/
26 silly mapToRegistry uri https://cli-npm.heroku.com/heroku-cli-addons
27 silly fetchNamedPackageData heroku-fork
28 silly mapToRegistry name heroku-fork
29 silly mapToRegistry using default registry
30 silly mapToRegistry registry https://cli-npm.heroku.com/
31 silly mapToRegistry uri https://cli-npm.heroku.com/heroku-fork
32 silly fetchNamedPackageData heroku-git
33 silly mapToRegistry name heroku-git
34 silly mapToRegistry using default registry
35 silly mapToRegistry registry https://cli-npm.heroku.com/
36 silly mapToRegistry uri https://cli-npm.heroku.com/heroku-git
37 silly fetchNamedPackageData heroku-local
38 silly mapToRegistry name heroku-local
39 silly mapToRegistry using default registry
40 silly mapToRegistry registry https://cli-npm.heroku.com/
41 silly mapToRegistry uri https://cli-npm.heroku.com/heroku-local
42 silly fetchNamedPackageData heroku-orgs
43 silly mapToRegistry name heroku-orgs
44 silly mapToRegistry using default registry
45 silly mapToRegistry registry https://cli-npm.heroku.com/
46 silly mapToRegistry uri https://cli-npm.heroku.com/heroku-orgs
47 silly fetchNamedPackageData heroku-pipelines
48 silly mapToRegistry name heroku-pipelines
49 silly mapToRegistry using default registry
50 silly mapToRegistry registry https://cli-npm.heroku.com/
51 silly mapToRegistry uri https://cli-npm.heroku.com/heroku-pipelines
52 silly fetchNamedPackageData heroku-run
53 silly mapToRegistry name heroku-run
54 silly mapToRegistry using default registry
55 silly mapToRegistry registry https://cli-npm.heroku.com/
56 silly mapToRegistry uri https://cli-npm.heroku.com/heroku-run
57 silly fetchNamedPackageData heroku-spaces
58 silly mapToRegistry name heroku-spaces
59 silly mapToRegistry using default registry
60 silly mapToRegistry registry https://cli-npm.heroku.com/
61 silly mapToRegistry uri https://cli-npm.heroku.com/heroku-spaces
62 silly fetchNamedPackageData heroku-status
63 silly mapToRegistry name heroku-status
64 silly mapToRegistry using default registry
65 silly mapToRegistry registry https://cli-npm.heroku.com/
66 silly mapToRegistry uri https://cli-npm.heroku.com/heroku-status
67 verbose request uri https://cli-npm.heroku.com/heroku-apps
68 verbose request no auth needed
69 info attempt registry request try #1 at 13:30:47
70 verbose request id c46751ecd6415e99
71 http request GET https://cli-npm.heroku.com/heroku-apps
72 verbose request uri https://cli-npm.heroku.com/heroku-cli-addons
73 verbose request no auth needed
74 info attempt registry request try #1 at 13:30:47
75 http request GET https://cli-npm.heroku.com/heroku-cli-addons
76 verbose request uri https://cli-npm.heroku.com/heroku-fork
77 verbose request no auth needed
78 info attempt registry request try #1 at 13:30:47
79 http request GET https://cli-npm.heroku.com/heroku-fork
80 verbose request uri https://cli-npm.heroku.com/heroku-git
81 verbose request no auth needed
82 info attempt registry request try #1 at 13:30:47
83 http request GET https://cli-npm.heroku.com/heroku-git
84 verbose request uri https://cli-npm.heroku.com/heroku-local
85 verbose request no auth needed
86 info attempt registry request try #1 at 13:30:47
87 http request GET https://cli-npm.heroku.com/heroku-local
88 verbose request uri https://cli-npm.heroku.com/heroku-orgs
89 verbose request no auth needed
90 info attempt registry request try #1 at 13:30:47
91 http request GET https://cli-npm.heroku.com/heroku-orgs
92 verbose request uri https://cli-npm.heroku.com/heroku-pipelines
93 verbose request no auth needed
94 info attempt registry request try #1 at 13:30:47
95 http request GET https://cli-npm.heroku.com/heroku-pipelines
96 verbose request uri https://cli-npm.heroku.com/heroku-run
97 verbose request no auth needed
98 info attempt registry request try #1 at 13:30:47
99 http request GET https://cli-npm.heroku.com/heroku-run
100 verbose request uri https://cli-npm.heroku.com/heroku-spaces
101 verbose request no auth needed
102 info attempt registry request try #1 at 13:30:47
103 http request GET https://cli-npm.heroku.com/heroku-spaces
104 verbose request uri https://cli-npm.heroku.com/heroku-status
105 verbose request no auth needed
106 info attempt registry request try #1 at 13:30:47
107 http request GET https://cli-npm.heroku.com/heroku-status
108 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
109 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
110 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
111 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
112 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
113 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
114 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
115 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
116 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
117 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
118 info attempt registry request try #2 at 13:31:18
119 http request GET https://cli-npm.heroku.com/heroku-status
120 info attempt registry request try #2 at 13:31:18
121 http request GET https://cli-npm.heroku.com/heroku-run
122 info attempt registry request try #2 at 13:31:18
123 http request GET https://cli-npm.heroku.com/heroku-pipelines
124 info attempt registry request try #2 at 13:31:18
125 http request GET https://cli-npm.heroku.com/heroku-cli-addons
126 info attempt registry request try #2 at 13:31:18
127 http request GET https://cli-npm.heroku.com/heroku-spaces
128 info attempt registry request try #2 at 13:31:18
129 http request GET https://cli-npm.heroku.com/heroku-local
130 info attempt registry request try #2 at 13:31:18
131 http request GET https://cli-npm.heroku.com/heroku-orgs
132 info attempt registry request try #2 at 13:31:18
133 http request GET https://cli-npm.heroku.com/heroku-git
134 info attempt registry request try #2 at 13:31:18
135 http request GET https://cli-npm.heroku.com/heroku-fork
136 info attempt registry request try #2 at 13:31:18
137 http request GET https://cli-npm.heroku.com/heroku-apps
138 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
139 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
140 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
141 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
142 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
143 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
144 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
145 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
146 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
147 info retry will retry, error on last attempt: Error: connect ETIMEDOUT 54.230.109.152:443
148 info attempt registry request try #3 at 13:32:39
149 http request GET https://cli-npm.heroku.com/heroku-run
150 info attempt registry request try #3 at 13:32:39
151 http request GET https://cli-npm.heroku.com/heroku-status
152 info attempt registry request try #3 at 13:32:39
153 http request GET https://cli-npm.heroku.com/heroku-pipelines
154 info attempt registry request try #3 at 13:32:39
155 http request GET https://cli-npm.heroku.com/heroku-apps
156 info attempt registry request try #3 at 13:32:39
157 http request GET https://cli-npm.heroku.com/heroku-fork
158 info attempt registry request try #3 at 13:32:39
159 http request GET https://cli-npm.heroku.com/heroku-spaces
160 info attempt registry request try #3 at 13:32:39
161 http request GET https://cli-npm.heroku.com/heroku-local
162 info attempt registry request try #3 at 13:32:39
163 http request GET https://cli-npm.heroku.com/heroku-git
164 info attempt registry request try #3 at 13:32:39
165 http request GET https://cli-npm.heroku.com/heroku-cli-addons
166 info attempt registry request try #3 at 13:32:39
167 http request GET https://cli-npm.heroku.com/heroku-orgs
168 silly fetchPackageMetaData Error: connect ETIMEDOUT 54.230.109.152:443
168 silly fetchPackageMetaData at Object.exports._errnoException (util.js:856:11)
168 silly fetchPackageMetaData at exports._exceptionWithHostPort (util.js:879:20)
168 silly fetchPackageMetaData at TCPConnectWrap.afterConnect as oncomplete
168 silly fetchPackageMetaData error for heroku-status { [Error: connect ETIMEDOUT 54.230.109.152:443]
168 silly fetchPackageMetaData code: 'ETIMEDOUT',
168 silly fetchPackageMetaData errno: 'ETIMEDOUT',
168 silly fetchPackageMetaData syscall: 'connect',
168 silly fetchPackageMetaData address: '54.230.109.152',
168 silly fetchPackageMetaData port: 443 }
169 silly fetchPackageMetaData Error: connect ETIMEDOUT 54.230.109.152:443
169 silly fetchPackageMetaData at Object.exports._errnoException (util.js:856:11)
169 silly fetchPackageMetaData at exports._exceptionWithHostPort (util.js:879:20)
169 silly fetchPackageMetaData at TCPConnectWrap.afterConnect as oncomplete
169 silly fetchPackageMetaData error for heroku-run { [Error: connect ETIMEDOUT 54.230.109.152:443]
169 silly fetchPackageMetaData code: 'ETIMEDOUT',
169 silly fetchPackageMetaData errno: 'ETIMEDOUT',
169 silly fetchPackageMetaData syscall: 'connect',
169 silly fetchPackageMetaData address: '54.230.109.152',
169 silly fetchPackageMetaData port: 443 }
170 silly fetchPackageMetaData Error: connect ETIMEDOUT 54.230.109.152:443
170 silly fetchPackageMetaData at Object.exports._errnoException (util.js:856:11)
170 silly fetchPackageMetaData at exports._exceptionWithHostPort (util.js:879:20)
170 silly fetchPackageMetaData at TCPConnectWrap.afterConnect as oncomplete
170 silly fetchPackageMetaData error for heroku-orgs { [Error: connect ETIMEDOUT 54.230.109.152:443]
170 silly fetchPackageMetaData code: 'ETIMEDOUT',
170 silly fetchPackageMetaData errno: 'ETIMEDOUT',
170 silly fetchPackageMetaData syscall: 'connect',
170 silly fetchPackageMetaData address: '54.230.109.152',
170 silly fetchPackageMetaData port: 443 }
171 silly fetchPackageMetaData Error: connect ETIMEDOUT 54.230.109.152:443
171 silly fetchPackageMetaData at Object.exports._errnoException (util.js:856:11)
171 silly fetchPackageMetaData at exports._exceptionWithHostPort (util.js:879:20)
171 silly fetchPackageMetaData at TCPConnectWrap.afterConnect as oncomplete
171 silly fetchPackageMetaData error for heroku-cli-addons { [Error: connect ETIMEDOUT 54.230.109.152:443]
171 silly fetchPackageMetaData code: 'ETIMEDOUT',
171 silly fetchPackageMetaData errno: 'ETIMEDOUT',
171 silly fetchPackageMetaData syscall: 'connect',
171 silly fetchPackageMetaData address: '54.230.109.152',
171 silly fetchPackageMetaData port: 443 }
172 silly fetchPackageMetaData Error: connect ETIMEDOUT 54.230.109.152:443
172 silly fetchPackageMetaData at Object.exports._errnoException (util.js:856:11)
172 silly fetchPackageMetaData at exports._exceptionWithHostPort (util.js:879:20)
172 silly fetchPackageMetaData at TCPConnectWrap.afterConnect as oncomplete
172 silly fetchPackageMetaData error for heroku-pipelines { [Error: connect ETIMEDOUT 54.230.109.152:443]
172 silly fetchPackageMetaData code: 'ETIMEDOUT',
172 silly fetchPackageMetaData errno: 'ETIMEDOUT',
172 silly fetchPackageMetaData syscall: 'connect',
172 silly fetchPackageMetaData address: '54.230.109.152',
172 silly fetchPackageMetaData port: 443 }
173 silly fetchPackageMetaData Error: connect ETIMEDOUT 54.230.109.152:443
173 silly fetchPackageMetaData at Object.exports._errnoException (util.js:856:11)
173 silly fetchPackageMetaData at exports._exceptionWithHostPort (util.js:879:20)
173 silly fetchPackageMetaData at TCPConnectWrap.afterConnect as oncomplete
173 silly fetchPackageMetaData error for heroku-git { [Error: connect ETIMEDOUT 54.230.109.152:443]
173 silly fetchPackageMetaData code: 'ETIMEDOUT',
173 silly fetchPackageMetaData errno: 'ETIMEDOUT',
173 silly fetchPackageMetaData syscall: 'connect',
173 silly fetchPackageMetaData address: '54.230.109.152',
173 silly fetchPackageMetaData port: 443 }
174 silly fetchPackageMetaData Error: connect ETIMEDOUT 54.230.109.152:443
174 silly fetchPackageMetaData at Object.exports._errnoException (util.js:856:11)
174 silly fetchPackageMetaData at exports._exceptionWithHostPort (util.js:879:20)
174 silly fetchPackageMetaData at TCPConnectWrap.afterConnect as oncomplete
174 silly fetchPackageMetaData error for heroku-fork { [Error: connect ETIMEDOUT 54.230.109.152:443]
174 silly fetchPackageMetaData code: 'ETIMEDOUT',
174 silly fetchPackageMetaData errno: 'ETIMEDOUT',
174 silly fetchPackageMetaData syscall: 'connect',
174 silly fetchPackageMetaData address: '54.230.109.152',
174 silly fetchPackageMetaData port: 443 }
175 silly fetchPackageMetaData Error: connect ETIMEDOUT 54.230.109.152:443
175 silly fetchPackageMetaData at Object.exports._errnoException (util.js:856:11)
175 silly fetchPackageMetaData at exports._exceptionWithHostPort (util.js:879:20)
175 silly fetchPackageMetaData at TCPConnectWrap.afterConnect as oncomplete
175 silly fetchPackageMetaData error for heroku-apps { [Error: connect ETIMEDOUT 54.230.109.152:443]
175 silly fetchPackageMetaData code: 'ETIMEDOUT',
175 silly fetchPackageMetaData errno: 'ETIMEDOUT',
175 silly fetchPackageMetaData syscall: 'connect',
175 silly fetchPackageMetaData address: '54.230.109.152',
175 silly fetchPackageMetaData port: 443 }
176 silly fetchPackageMetaData Error: connect ETIMEDOUT 54.230.109.152:443
176 silly fetchPackageMetaData at Object.exports._errnoException (util.js:856:11)
176 silly fetchPackageMetaData at exports._exceptionWithHostPort (util.js:879:20)
176 silly fetchPackageMetaData at TCPConnectWrap.afterConnect as oncomplete
176 silly fetchPackageMetaData error for heroku-local { [Error: connect ETIMEDOUT 54.230.109.152:443]
176 silly fetchPackageMetaData code: 'ETIMEDOUT',
176 silly fetchPackageMetaData errno: 'ETIMEDOUT',
176 silly fetchPackageMetaData syscall: 'connect',
176 silly fetchPackageMetaData address: '54.230.109.152',
176 silly fetchPackageMetaData port: 443 }
177 silly fetchPackageMetaData Error: connect ETIMEDOUT 54.230.109.152:443
177 silly fetchPackageMetaData at Object.exports._errnoException (util.js:856:11)
177 silly fetchPackageMetaData at exports._exceptionWithHostPort (util.js:879:20)
177 silly fetchPackageMetaData at TCPConnectWrap.afterConnect as oncomplete
177 silly fetchPackageMetaData error for heroku-spaces { [Error: connect ETIMEDOUT 54.230.109.152:443]
177 silly fetchPackageMetaData code: 'ETIMEDOUT',
177 silly fetchPackageMetaData errno: 'ETIMEDOUT',
177 silly fetchPackageMetaData syscall: 'connect',
177 silly fetchPackageMetaData address: '54.230.109.152',
177 silly fetchPackageMetaData port: 443 }
178 silly rollbackFailedOptional Starting
179 silly rollbackFailedOptional Finishing
180 silly runTopLevelLifecycles Starting
181 silly runTopLevelLifecycles Finishing
182 silly install printInstalled
183 verbose stack Error: connect ETIMEDOUT 54.230.109.152:443
183 verbose stack at Object.exports._errnoException (util.js:856:11)
183 verbose stack at exports._exceptionWithHostPort (util.js:879:20)
183 verbose stack at TCPConnectWrap.afterConnect as oncomplete
184 verbose cwd C:\Users\Leon\AppData\Local\heroku
185 error Windows_NT 6.1.7601
186 error argv "C:\Users\Leon\AppData\Local\heroku\node-v5.7.1-windows-x86\bin\node.exe" "C:\Users\Leon\AppData\Local\heroku\node-v5.7.1-windows-x86\lib\node_modules\npm\cli.js" "install" "heroku-apps" "heroku-cli-addons" "heroku-fork" "heroku-git" "heroku-local" "heroku-orgs" "heroku-pipelines" "heroku-run" "heroku-spaces" "heroku-status"
187 error node v5.7.1
188 error npm v3.3.10
189 error code ETIMEDOUT
190 error errno ETIMEDOUT
191 error syscall connect
192 error network connect ETIMEDOUT 54.230.109.152:443
192 error network This is most likely not a problem with npm itself
192 error network and is related to network connectivity.
192 error network In most cases you are behind a proxy or have bad network settings.
192 error network
192 error network If you are behind a proxy, please make sure that the
192 error network 'proxy' config is set properly. See: 'npm help config'
193 verbose exit [ 1, true ]

[ransombriggs]

@leonkidd are you behind a network proxy?

[leonkidd]

@ransombriggs nop

[ransombriggs]

@leonkidd Windows Firewall or Antivirus software can block connections in this manner, do you have either installed / running? Also, what version of Windows are you running? I would like to try and reproduce this locally.

[leonkidd]

@ransombriggs Firewall was shutdown and My OS system is windows 7 Enterprise. It just work fine right now, but few minutes age it was not. I have no idea that I just try again again and again....
Thanks a lot !@ransombriggs

`ist of available stacks","needsApp":true,"needsAuth":true},{"topic":"stack","com
mand":"set","needsApp":true,"needsAuth":true,"help":"\nExample:\n\n $ heroku st
ack:set cedar-14 -a myapp\n Stack set. Next release on myapp will use cedar-14.
\n Run git push heroku master to create a new release on myapp.","args":[{"name
":"stack"}]}],"name":"heroku-apps","version":"1.7.3"}
! "Leon" Sid: S-1-5-21-367982105-2523211310-3914911705-1000
! error getting commands pid 6588 exit 1

C:\Users\Leon>heroku login
heroku-cli: Installing core plugins... done
Enter your Heroku credentials.`

[ransombriggs]

@leonkidd sorry, your last message was not totally clear, is everything working for you right now?

[leonkidd]

@ransombriggs Yes, It was working after I try several times. But I still don't find the cause.