The test suite for this is a bit finnicky because root rights are required to run dtrace. By default we run the dtrace.test.js file with 'sudo'. Use this to skip the dtrace tests: SKIP_DTRACE=1 make test Note taht 'make test09' is busted because dtrace-provider seems busted with node 0.9.1 at least.
…obes) dtrace-provider is still in *dependencies* to strongly encourage installing it. However I want bunyan.js to be useable for basic usage standalone.
- before this, if there were no non-raw streams on the logger the `str` for the dtrace probe.fire would not be created - ensure that with no non-raw streams we only render a record's JSON string if the dtrace probe is enabled
from the likes of `WError` or `VError` error classes from [verror](https://github.com/davepacheco/node-verror) and [restify v2.0](https://github.com/mcavage/node-restify).
…es' field that isn't a response object, but a string.
Looks like this: * * * * The Bunyan CLI crashed! Please report this issue: * * https://github.com/trentm/node-bunyan/issues/new * * and include the following Bunyan details the log file * (or section of log file) on which the Bunyan CLI crashed. * * * * node version: v0.8.9 * bunyan version: 0.14.2 * argv: [ 'node', '/Users/trentm/tm/node-bunyan-0.x/bin/bunyan' ] * stack: * TypeError: Object.keys called on non-object * at Function.keys (native) * at emitRecord (/Users/trentm/tm/node-bunyan-0.x/bin/bunyan:718:14) * at handleLogLine (/Users/trentm/tm/node-bunyan-0.x/bin/bunyan:507:12) * at Socket.<anonymous> (/Users/trentm/tm/node-bunyan-0.x/bin/bunyan:856:7) * at Socket.EventEmitter.emit (events.js:88:17) * at Pipe.onread (net.js:391:31) * * *
…is an object instead of a string. See issue#38 for the same with `req.body`.