bunyan tool crashes with Object.keys called on non-object

[vincentcr]

while running the tool like this:

$ myprog 2>&1 | ./node_modules/.bin/bunyan

i wil get this error sometimes:

/Users/vincent/devel/server/node_modules/bunyan/bin/bunyan:510
        Object.keys(headers).map(
               ^
TypeError: Object.keys called on non-object
    at Function.keys (native)
    at emitRecord (/Users/vincent/devel/server/node_modules/bunyan/bin/bunyan:510:16)
    at handleLogLine (/Users/vincent/devel/server/node_modules/bunyan/bin/bunyan:415:12)
    at Socket.<anonymous> (/Users/vincent/devel/server/node_modules/bunyan/bin/bunyan:674:7)
    at Socket.EventEmitter.emit (events.js:88:17)
    at Pipe.onread (net.js:398:31)
make: *** [run] Error 1

[trentm]

@vincentcr Can you post an example log record that causes this problem. I'm guessing that you have a "req" top-level field in the log record that does NOT have a headers sub field. Just want to confirm that, then I can get bunyan to handle that gracefully.

[vincentcr]

Hi Trent,

you are correct, the entry contains a req top-level field without a headers sub-field, like this:

"req":{
 "reqid":"18abcf50-e1a2-11e1-ad55-959773e9549f",
 "method":"GET",
 "url":"/",
 "user-agent":"curl/7.21.4 (universal-apple-darwin11.0) libcurl/7.21.4 OpenSSL/0.9.8r zlib/1.2.5",
 "accept":"*/*",
 "remote-address":"127.0.0.1",
 "host":"localhost:3000",
 "http-version":"1.1",
 "status":200,
"content-length":"14"}

[trentm]

In 0.11.2 release.