Failed batch (array form) executes call back with empty error object.

[nmartin867]

Failed batch() executes call back function with empty error object. I would expect the WriteError in the callback. Is this correct?

Code to repo:

http://pastebin.com/XCL7LPTS

[rvagg]

yeah, should be something more than {}

[jcrugzz]

The problem is with new WriteError(err). It takes the err ( [Error: value cannot be null or undefined]) and turns it into {}. Not particularly sure why but somehow the error creation from errno is not returning a proper error. @rvagg thoughts?

[rvagg]

It doesn't turn in to a {}, it's just util/format doing that for console.log() since it doesn't recognise it as an Error object because it can't return '[object Error]' from an Object.prototype.toString(e).

We'll see how this goes.

But in the mean time, you can still reach in to the object and fetch properties out of it, you can print a stack trace and anything else you can do with an Error object, you just can't console.log() or util.format() it in to something nice.

[rvagg]

also, instead of if (err) return console.log(err) do an if (err) throw err and you should see the error turn up. not production-worthy but neither is console.log().

[jcrugzz]

Ahh ok that makes sense then.

[rvagg]

nodejs/node-v0.x-archive@684dd28

Landed in Node master, I imagine it'll be available in 0.11+ and not backported to 0.10, but at least it's there!

[juliangruber]

core commit, whoop whooop!