Publish fails but returns success

[ssandler]

On the client, I ran reggie publish:
%reggie -u http://127.0.0.1:8280 publish uid2-0.0.2.tgz successfully published version 0.0.2 of uid2: http://127.0.0.1:8125/package/uid2/0.0.2 done

On the server side, an error is written to stdout. So the package is not registered, but it still returns success and the client thinks it's been registered.
Cannot stat file /data/packages/uid2-0.0.2.tgz: Error: ENOENT, stat '/data/packages/uid2-0.0.2.tgz'

I'm not sure why it can't stat that file. When I try to publish again, it works fine and shows Registered package uid2@0.0.2 on the server side (client side output is the same).

I've been publishing several things and I've found roughly a 50% error rate, retrying always works.

Any ideas on fixing the "cannot stat" error as well as making the server return an error if it fails to register the package?

[mengstr]

I'm having the same problem. Publishing is reported as a success at the client but reggie actually failed. Retrying usually makes it work.

Cannot stat file /home/reggie/packages/queueman-0.1.6.tgz: Error: ENOENT, stat '/home/reggie/packages/queueman-0.1.6.tgz'
Registered package queueman@0.1.7

MatsMac:queueman matseng$ ./publish.sh 
v0.1.6
queueman-0.1.6.tgz
successfully published version 0.1.6 of queueman: http://npm.example.com:42009/package/queueman/0.1.6
done
MatsMac:queueman matseng$ ./publish.sh 
v0.1.7
queueman-0.1.7.tgz
successfully published version 0.1.7 of queueman: http://npm.example.com:42009/package/queueman/0.1.7
done

MatsMac:queueman matseng$ cat publish.sh 
#!/bin/bash
npm version patch
reggie -u http://npm.example.com:42009 publish