Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

GET returning 404 on fetch on 'node-sixense' package #4274

Closed
ironman9967 opened this Issue · 7 comments

4 participants

@ironman9967

I published the 'node-sixense' package. When I try to install it, I receive a 404 on the GET command to fetch the .tgz file. Please let me know if I have something configured incorrectly or if there is a problem with the package itself. Here is the npm-debug.log:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'install',
1 verbose cli 'node-sixense' ]
2 info using npm@1.3.14
3 info using node@v0.10.22
4 verbose node symlink C:\Program Files\nodejs\node.exe
5 verbose cache add [ 'node-sixense', null ]
6 verbose cache add name=undefined spec="node-sixense" args=["node-sixense",null]
7 verbose parsed url { protocol: null,
7 verbose parsed url slashes: null,
7 verbose parsed url auth: null,
7 verbose parsed url host: null,
7 verbose parsed url port: null,
7 verbose parsed url hostname: null,
7 verbose parsed url hash: null,
7 verbose parsed url search: null,
7 verbose parsed url query: null,
7 verbose parsed url pathname: 'node-sixense',
7 verbose parsed url path: 'node-sixense',
7 verbose parsed url href: 'node-sixense' }
8 silly lockFile c385eaa8-node-sixense node-sixense
9 verbose lock node-sixense C:\Users\thester\AppData\Roaming\npm-cache\c385eaa8-node-sixense.lock
10 silly lockFile c385eaa8-node-sixense node-sixense
11 silly lockFile c385eaa8-node-sixense node-sixense
12 verbose addNamed [ 'node-sixense', '' ]
13 verbose addNamed [ null, '' ]
14 silly lockFile 72f37a18-node-sixense node-sixense@
15 verbose lock node-sixense@ C:\Users\thester\AppData\Roaming\npm-cache\72f37a18-node-sixense.lock
16 silly addNameRange { name: 'node-sixense', range: '
', hasData: false }
17 verbose url raw node-sixense
18 verbose url resolving [ 'https://registry.npmjs.org/', './node-sixense' ]
19 verbose url resolved https://registry.npmjs.org/node-sixense
20 info trying registry request attempt 1 at 13:32:16
21 http GET https://registry.npmjs.org/node-sixense
22 http 200 https://registry.npmjs.org/node-sixense
23 silly registry.get cb [ 200,
23 silly registry.get { vary: 'Accept',
23 silly registry.get server: 'CouchDB/1.5.0 (Erlang OTP/R15B03)',
23 silly registry.get etag: '"C8GM1YTVMOUTLPV363MNFWYZH"',
23 silly registry.get date: 'Mon, 09 Dec 2013 18:32:16 GMT',
23 silly registry.get 'content-type': 'application/json',
23 silly registry.get 'content-length': '103859' } ]
24 silly addNameRange number 2 { name: 'node-sixense', range: '*', hasData: true }
25 silly addNameRange versions [ 'node-sixense',
25 silly addNameRange [ '0.0.3',
25 silly addNameRange '0.0.4',
25 silly addNameRange '0.0.1',
25 silly addNameRange '0.0.6',
25 silly addNameRange '0.0.7-1',
25 silly addNameRange '0.0.8',
25 silly addNameRange '0.0.9',
25 silly addNameRange '0.1.0',
25 silly addNameRange '0.1.1',
25 silly addNameRange '0.2.0',
25 silly addNameRange '0.2.1',
25 silly addNameRange '0.2.2',
25 silly addNameRange '0.2.3',
25 silly addNameRange '0.2.5',
25 silly addNameRange '0.2.6',
25 silly addNameRange '0.2.7' ] ]
26 verbose addNamed [ 'node-sixense', '0.2.7' ]
27 verbose addNamed [ '0.2.7', '0.2.7' ]
28 silly lockFile a2036c3c-node-sixense-0-2-7 node-sixense@0.2.7
29 verbose lock node-sixense@0.2.7 C:\Users\thester\AppData\Roaming\npm-cache\a2036c3c-node-sixense-0-2-7.lock
30 silly lockFile 7a9a2fb2-e-sixense-node-sixense-0-2-7-tgz https://registry.npmjs.org/node-sixense/-/node-sixense-0.2.7.tgz
31 verbose lock https://registry.npmjs.org/node-sixense/-/node-sixense-0.2.7.tgz C:\Users\thester\AppData\Roaming\npm-cache\7a9a2fb2-e-sixense-node-sixense-0-2-7-tgz.lock
32 verbose addRemoteTarball [ 'https://registry.npmjs.org/node-sixense/-/node-sixense-0.2.7.tgz',
32 verbose addRemoteTarball 'b61f43c2b1b489914a1d7d171e4e14e235377c91' ]
33 info retry fetch attempt 1 at 13:32:17
34 verbose fetch to= C:\Users\thester\AppData\Local\Temp\npm-21112-LujgzTgJ\1386613937178-0.23620038642548025\tmp.tgz
35 http GET https://registry.npmjs.org/node-sixense/-/node-sixense-0.2.7.tgz
36 http 404 https://registry.npmjs.org/node-sixense/-/node-sixense-0.2.7.tgz
37 error fetch failed https://registry.npmjs.org/node-sixense/-/node-sixense-0.2.7.tgz
38 silly lockFile 7a9a2fb2-e-sixense-node-sixense-0-2-7-tgz https://registry.npmjs.org/node-sixense/-/node-sixense-0.2.7.tgz
39 silly lockFile 7a9a2fb2-e-sixense-node-sixense-0-2-7-tgz https://registry.npmjs.org/node-sixense/-/node-sixense-0.2.7.tgz
40 silly lockFile a2036c3c-node-sixense-0-2-7 node-sixense@0.2.7
41 silly lockFile a2036c3c-node-sixense-0-2-7 node-sixense@0.2.7
42 silly lockFile 72f37a18-node-sixense node-sixense@
43 silly lockFile 72f37a18-node-sixense node-sixense@
44 error Error: 404 Not Found
44 error at WriteStream. (C:\Program Files\nodejs\node_modules\npm\lib\utils\fetch.js:57:12)
44 error at WriteStream.EventEmitter.emit (events.js:117:20)
44 error at fs.js:1596:14
44 error at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:103:5
44 error at Object.oncomplete (fs.js:107:15)
45 error If you need help, you may report this log at:
45 error http://github.com/isaacs/npm/issues
45 error or email it to:
45 error npm-@googlegroups.com
46 error System Windows_NT 6.1.7601
47 error command "C:\Program Files\nodejs\\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "node-sixense"
48 error cwd C:\Users\thester\Projects\WebStorm[PROJECT_NAME]
49 error node -v v0.10.22
50 error npm -v 1.3.14
51 verbose exit [ 1, true ]

@robertkowalski
Collaborator

sounds like the problem from last week, @jhs?

@ironman9967

Just to update, I made some changes and published a newer version, 0.2.73. According to www.npmjs.org, the latest package is 0.2.71 which has the same issue as 0.2.7. However, the registry link (https://registry.npmjs.org/node-sixense/-/node-sixense-0.2.73.tgz) seems to work correctly.

@timoxley
Collaborator

@ironman9967 can you try unpublishing and republishing both versions?

@robertkowalski
Collaborator
{"error":"not_found","reason":"Document is missing attachment"}
@ironman9967

I executed 'npm unpublish node-sixense --force' successfully

When I ran 'npm publish' from the project directory, I received this log:

npm http PUT https://registry.npmjs.org/node-sixense
npm http 409 https://registry.npmjs.org/node-sixense
npm http GET https://registry.npmjs.org/node-sixense
npm http 200 https://registry.npmjs.org/node-sixense
npm http PUT https://registry.npmjs.org/node-sixense
npm http 409 https://registry.npmjs.org/node-sixense
npm ERR! Error: conflict Document update conflict.: node-sixense
npm ERR! at RegClient. (/usr/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:275:14)
npm ERR! at Request.self.callback (/usr/lib/node_modules/npm/node_modules/request/request.js:123:22)
npm ERR! at Request.EventEmitter.emit (events.js:98:17)
npm ERR! at Request. (/usr/lib/node_modules/npm/node_modules/request/request.js:893:14)
npm ERR! at Request.EventEmitter.emit (events.js:117:20)
npm ERR! at IncomingMessage. (/usr/lib/node_modules/npm/node_modules/request/request.js:844:12)
npm ERR! at IncomingMessage.EventEmitter.emit (events.js:117:20)
npm ERR! at _stream_readable.js:920:16
npm ERR! at process._tickCallback (node.js:415:13)
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/isaacs/npm/issues

npm ERR! System Linux 3.11.0-14-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "publish"
npm ERR! cwd /home/removed/Development/Projects/NodeSixense
npm ERR! node -v v0.10.24
npm ERR! npm -v 1.3.21
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/removed/Development/Projects/NodeSixense/npm-debug.log
npm ERR! not ok code 0

@timoxley
Collaborator

@ironman9967 There's been a lot of similar issues and I believe they've been due to the repository infrastructure changes recently. Can you upgrade npm… try again and report back?

@ironman9967

I upgraded npm to version 1.4.4, republished the package and it seems to work fine now!

I'm going to do some more testing, just to be sure, and I'll close the issue if all is well.

Thank you all very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.