publish: registry error parsing json #4655

Closed
seanmonstar opened this Issue Feb 12, 2014 · 7 comments

5 participants

@seanmonstar

I'm trying to push a new version. The only change to my package.json is the version number. It's valid JSON. npm test runs just fine. However, when I run npm publish, I get a json parse error.

PS D:\Users\Sean\Documents\Mozilla\intel> npm publish --verbose
npm info it worked if it ends with ok
npm verb cli [ 'C:\\Program Files\\nodejs\\\\node.exe',
npm verb cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
npm verb cli   'publish',
npm verb cli   '--verbose' ]
npm info using npm@1.3.11
npm info using node@v0.10.20
npm verb node symlink C:\Program Files\nodejs\\node.exe
npm verb publish [ '.' ]
npm verb cache add [ '.', null ]
npm verb cache add name=undefined spec="." args=[".",null]
npm verb parsed url { protocol: null,
npm verb parsed url   slashes: null,
npm verb parsed url   auth: null,
npm verb parsed url   host: null,
npm verb parsed url   port: null,
npm verb parsed url   hostname: null,
npm verb parsed url   hash: null,
npm verb parsed url   search: null,
npm verb parsed url   query: null,
npm verb parsed url   pathname: '.',
npm verb parsed url   path: '.',
npm verb parsed url   href: '.' }
npm verb lock . C:\Users\Sean\AppData\Roaming\npm-cache\3a52ce78-.lock
npm verb tar pack [ 'C:\\Users\\Sean\\AppData\\Local\\Temp\\npm-12428-T1LAXy0f\\1392188276626-0.7069167399313301\\tmp.tgz',
npm verb tar pack   '.' ]
npm verb tarball C:\Users\Sean\AppData\Local\Temp\npm-12428-T1LAXy0f\1392188276626-0.7069167399313301\tmp.tgz
npm verb folder .
npm verb lock tar://. C:\Users\Sean\AppData\Roaming\npm-cache\1f1177db-tar.lock
npm verb lock tar://C:\Users\Sean\AppData\Local\Temp\npm-12428-T1LAXy0f\1392188276626-0.7069167399313301\tmp.tgz C:\Users\Sean\AppData\Roaming\npm-cache\70f8a944-76626-0-7069167399313301-tmp-tgz.lock
npm verb tar unpack C:\Users\Sean\AppData\Local\Temp\npm-12428-T1LAXy0f\1392188276626-0.7069167399313301\tmp.tgz
npm verb lock tar://C:\Users\Sean\AppData\Local\Temp\npm-12428-T1LAXy0f\1392188276626-0.7069167399313301\package C:\Users\Sean\AppData\Roaming\npm-cache\d2cd88ad-76626-0-7069167399313301-package.lock
npm verb lock tar://C:\Users\Sean\AppData\Local\Temp\npm-12428-T1LAXy0f\1392188276626-0.7069167399313301\tmp.tgz C:\Users\Sean\AppData\Roaming\npm-cache\70f8a944-76626-0-7069167399313301-tmp-tgz.lock
npm verb tar pack [ 'C:\\Users\\Sean\\AppData\\Roaming\\npm-cache\\intel\\0.5.1\\package.tgz',
npm verb tar pack   'C:\\Users\\Sean\\AppData\\Local\\Temp\\npm-12428-T1LAXy0f\\1392188276626-0.7069167399313301\\package' ]
npm verb tarball C:\Users\Sean\AppData\Roaming\npm-cache\intel\0.5.1\package.tgz
npm verb folder C:\Users\Sean\AppData\Local\Temp\npm-12428-T1LAXy0f\1392188276626-0.7069167399313301\package
npm verb lock tar://C:\Users\Sean\AppData\Local\Temp\npm-12428-T1LAXy0f\1392188276626-0.7069167399313301\package C:\Users\Sean\AppData\Roaming\npm-cache\d2cd88ad-76626-0-7069167399313301-package.lock
npm verb lock tar://C:\Users\Sean\AppData\Roaming\npm-cache\intel\0.5.1\package.tgz C:\Users\Sean\AppData\Roaming\npm-cache\7e81fc12-pm-cache-intel-0-5-1-package-tgz.lock
npm verb lock C:\Users\Sean\AppData\Roaming\npm-cache\intel\0.5.1\package C:\Users\Sean\AppData\Roaming\npm-cache\fd8b7fab-ng-npm-cache-intel-0-5-1-package.lock
npm verb tar unpack C:\Users\Sean\AppData\Roaming\npm-cache\intel\0.5.1\package.tgz
npm verb lock tar://C:\Users\Sean\AppData\Roaming\npm-cache\intel\0.5.1\package C:\Users\Sean\AppData\Roaming\npm-cache\c56a6bd1-ng-npm-cache-intel-0-5-1-package.lock
npm verb lock tar://C:\Users\Sean\AppData\Roaming\npm-cache\intel\0.5.1\package.tgz C:\Users\Sean\AppData\Roaming\npm-cache\7e81fc12-pm-cache-intel-0-5-1-package-tgz.lock
npm verb chmod C:\Users\Sean\AppData\Roaming\npm-cache\intel\0.5.1\package.tgz 644
npm verb url raw intel
npm verb url resolving [ 'https://registry.npmjs.org/', './intel' ]
npm verb url resolved https://registry.npmjs.org/intel
npm info trying registry request attempt 1 at 22:57:56
npm http PUT https://registry.npmjs.org/intel
npm http 409 https://registry.npmjs.org/intel
npm verb url raw intel
npm verb url resolving [ 'https://registry.npmjs.org/', './intel' ]
npm verb url resolved https://registry.npmjs.org/intel
npm info trying registry request attempt 1 at 22:57:58
npm http GET https://registry.npmjs.org/intel
npm http 200 https://registry.npmjs.org/intel
npm verb uploading [ 'intel/-/intel-0.5.1.tgz/-rev/26-2e68ddd2f8427f73ff7ac8299dca79c6',
npm verb uploading   'C:\\Users\\Sean\\AppData\\Roaming\\npm-cache\\intel\\0.5.1\\package.tgz' ]
npm verb url raw intel/-/intel-0.5.1.tgz/-rev/26-2e68ddd2f8427f73ff7ac8299dca79c6
npm verb url resolving [ 'https://registry.npmjs.org/',
npm verb url resolving   './intel/-/intel-0.5.1.tgz/-rev/26-2e68ddd2f8427f73ff7ac8299dca79c6' ]
npm verb url resolved https://registry.npmjs.org/intel/-/intel-0.5.1.tgz/-rev/26-2e68ddd2f8427f73ff7ac8299dca79c6
npm info trying registry request attempt 1 at 22:57:58
npm http PUT https://registry.npmjs.org/intel/-/intel-0.5.1.tgz/-rev/26-2e68ddd2f8427f73ff7ac8299dca79c6
npm http 500 https://registry.npmjs.org/intel/-/intel-0.5.1.tgz/-rev/26-2e68ddd2f8427f73ff7ac8299dca79c6
npm verb bad json An internal server error occurred. Please try again later.
npm ERR! registry error parsing json
npm info retry will retry, error on last attempt: SyntaxError: Unexpected token A
npm info retry An internal server error occurred. Please try again later.
@Munter

I get similar errors:

npm info posttest slint@0.1.0
npm verb exit [ 0, true ]
npm info ok 
npm verb lock tar://. /home/munter/.npm/1f1177db-tar.lock
npm verb lock tar:///home/munter/tmp/npm-1995/1392216575833-0.1589245789218694/tmp.tgz /home/munter/.npm/fd1cfd49-75833-0-1589245789218694-tmp-tgz.lock
npm verb tar unpack /home/munter/tmp/npm-1995/1392216575833-0.1589245789218694/tmp.tgz
npm verb lock tar:///home/munter/tmp/npm-1995/1392216575833-0.1589245789218694/package /home/munter/.npm/a57a6729-75833-0-1589245789218694-package.lock
npm verb lock tar:///home/munter/tmp/npm-1995/1392216575833-0.1589245789218694/tmp.tgz /home/munter/.npm/fd1cfd49-75833-0-1589245789218694-tmp-tgz.lock
npm verb read json /home/munter/tmp/npm-1995/1392216575833-0.1589245789218694/package/package.json
npm verb from cache /home/munter/tmp/npm-1995/1392216575833-0.1589245789218694/package/package.json
npm verb tar pack [ '/home/munter/.npm/slint/0.1.0/package.tgz',
npm verb tar pack   '/home/munter/tmp/npm-1995/1392216575833-0.1589245789218694/package' ]
npm verb tarball /home/munter/.npm/slint/0.1.0/package.tgz
npm verb folder /home/munter/tmp/npm-1995/1392216575833-0.1589245789218694/package
npm verb lock tar:///home/munter/tmp/npm-1995/1392216575833-0.1589245789218694/package /home/munter/.npm/a57a6729-75833-0-1589245789218694-package.lock
npm verb lock tar:///home/munter/.npm/slint/0.1.0/package.tgz /home/munter/.npm/f9f503ab-nter-npm-slint-0-1-0-package-tgz.lock
npm verb lock /home/munter/.npm/slint/0.1.0/package /home/munter/.npm/cc854264-e-munter-npm-slint-0-1-0-package.lock
npm verb tar unpack /home/munter/.npm/slint/0.1.0/package.tgz
npm verb lock tar:///home/munter/.npm/slint/0.1.0/package /home/munter/.npm/6953317b-e-munter-npm-slint-0-1-0-package.lock
npm verb lock tar:///home/munter/.npm/slint/0.1.0/package.tgz /home/munter/.npm/f9f503ab-nter-npm-slint-0-1-0-package-tgz.lock
npm verb read json /home/munter/.npm/slint/0.1.0/package/package.json
npm verb from cache /home/munter/.npm/slint/0.1.0/package/package.json
npm verb chmod /home/munter/.npm/slint/0.1.0/package.tgz 644
npm verb chown /home/munter/.npm/slint/0.1.0/package.tgz [ 1000, 1000 ]
npm verb url raw slint
npm verb url resolving [ 'https://registry.npmjs.org/', './slint' ]
npm verb url resolved https://registry.npmjs.org/slint
npm info trying registry request attempt 1 at 15:49:43
npm http PUT https://registry.npmjs.org/slint
npm http 409 https://registry.npmjs.org/slint
npm verb url raw slint
npm verb url resolving [ 'https://registry.npmjs.org/', './slint' ]
npm verb url resolved https://registry.npmjs.org/slint
npm info trying registry request attempt 1 at 15:49:44
npm http GET https://registry.npmjs.org/slint
npm http 200 https://registry.npmjs.org/slint
npm verb uploading [ 'slint/-/slint-0.1.0.tgz/-rev/5-91a7c930aa2b1f161d4cfb892be01cb6',
npm verb uploading   '/home/munter/.npm/slint/0.1.0/package.tgz' ]
npm verb url raw slint/-/slint-0.1.0.tgz/-rev/5-91a7c930aa2b1f161d4cfb892be01cb6
npm verb url resolving [ 'https://registry.npmjs.org/',
npm verb url resolving   './slint/-/slint-0.1.0.tgz/-rev/5-91a7c930aa2b1f161d4cfb892be01cb6' ]
npm verb url resolved https://registry.npmjs.org/slint/-/slint-0.1.0.tgz/-rev/5-91a7c930aa2b1f161d4cfb892be01cb6
npm info trying registry request attempt 1 at 15:49:44
npm http PUT https://registry.npmjs.org/slint/-/slint-0.1.0.tgz/-rev/5-91a7c930aa2b1f161d4cfb892be01cb6
npm http 500 https://registry.npmjs.org/slint/-/slint-0.1.0.tgz/-rev/5-91a7c930aa2b1f161d4cfb892be01cb6
npm verb bad json An internal server error occurred. Please try again later.
npm ERR! registry error parsing json
npm info retry will retry, error on last attempt: SyntaxError: Unexpected token A
npm info retry An internal server error occurred. Please try again later.
npm info trying registry request attempt 2 at 15:49:55
npm http PUT https://registry.npmjs.org/slint/-/slint-0.1.0.tgz/-rev/5-91a7c930aa2b1f161d4cfb892be01cb6
npm ERR! cb() never called!
npm ERR! not ok code 0
@rlidwka

"An internal server error occurred. Please try again later."

@seanmonstar seanmonstar referenced this issue in seanmonstar/intel Feb 13, 2014
Closed

error if null is passed to Logger.log() #17

@Munter

My error from earlier is no longer relevant as of a few minutes ago. The package is publishing fine for me now

@seanmonstar

Mine still occurs.

@seanmonstar

I was finally able to publish. I made no changes on my part, just tried every few hours.

@seanmonstar

And just hit it again pushing a newer version.

@othiym23

We were having some fun times getting everything up and stable with the registry back in February. As far as I know, this has subsequently been almost entirely remedied. Let us know if you run into new problems. (Also, make sure to regularly update npm – npm@1.3.x can no longer publish to the registry.) Sorry for the inconvenience!

@othiym23 othiym23 closed this Sep 17, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment