Error: conflict Document update conflict #4366
Comments
I'm having the same issue npm ERR! Error: conflict Document update conflict.: sails-generate-model
npm ERR! at RegClient.<anonymous> (/Users/mike/.nvm/v0.10.25/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:275:14)
npm ERR! at Request.self.callback (/Users/mike/.nvm/v0.10.25/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.<anonymous> (/Users/mike/.nvm/v0.10.25/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.<anonymous> (/Users/mike/.nvm/v0.10.25/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 Darwin 11.4.2
npm ERR! command "/Users/mike/.nvm/v0.10.25/bin/node" "/Users/mike/.nvm/v0.10.25/bin/npm" "publish"
npm ERR! cwd /code/oss/generators/model
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.24
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /code/oss/generators/model/npm-debug.log
npm ERR! not ok code 0
|
also just started hitting this publishing:
|
Got this error also, but updating to the latest version of npm (v1.4.2) fixed the issue for me. |
Is this still a problem for you? This looks like it might have been related to the registry as implemented at the time (February 2014). Now, almost a year later, the registry implementation has changed substantially. Are you still seeing errors of this type? We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and open a new issue!) Thanks! |
This bug can be closed. Thanks.
|
Closing as resolved. |
Attempting to log in, I get the errors below. I try following the solution suggested on #4093, but this doesn't seem to solve my problem.
The text was updated successfully, but these errors were encountered: