/lib/s3.js putFile throws { [Error: read ECONNRESET] code: 'ECONNRESET', errno: 'ECONNRESET', syscall: 'read' }

[bitliner]

i'm using grunt-s3 to upload files to s3.
When the function putFile of lib/s3.js of knox module is called, it throws

{ [Error: read ECONNRESET] code: 'ECONNRESET', errno: 'ECONNRESET', syscall: 'read' }

[bitliner]

with node-v0.10.12

[domenic]

You should not forget to attach 'error' handlers to the request object returned from putFile.

[bitliner]

@domenic putFile doesn't return anything.
The req object, returned by self.putStream(), has a callback, whose error is that displayed above.

[bitliner]

Sometimes the syscall specified in the error is 'write' instead of 'read'

[domenic]

You are partially right. It does return an event emitter, but the event emitter was not getting errors forwarded to it from the underlying request.

With the upcoming release errors will be trapped and either forwarded to your callback if the callback hasn't been called yet, or forwarded to the returned event emitter if it has been called.

Also relevant: the discussion in #114, about whether you should have to listen to these errors at all or if we should maybe just swallow them if you get a second error after having already called you back with an error or result.