Permalink
Commits on Oct 11, 2012
  1. prepare for 0.14.5 release

    trentm committed Oct 11, 2012
  2. prep for future dev

    trentm committed Oct 11, 2012
  3. prepare for 0.14.4 release

    trentm committed Oct 11, 2012
  4. fix a bad error in 0.14.3

    trentm committed Oct 11, 2012
  5. prep for future dev

    trentm committed Oct 11, 2012
  6. prepare for 0.14.3 release

    trentm committed Oct 11, 2012
  7. minor edit

    trentm committed Oct 11, 2012
  8. Improve error serialization to walk the chain of `.cause()` errors

    trentm committed Oct 11, 2012
    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).
Commits on Oct 10, 2012
  1. prep for future dev

    trentm committed Oct 10, 2012
  2. prepare for 0.14.2 release

    trentm committed Oct 10, 2012
  3. [issue #45] Fix bunyan CLI (default output mode) to not crash on a 'r…

    trentm committed Oct 10, 2012
    …es' field that isn't a response object, but a string.
  4. Add an uncaughtException handler to request a ticket and details.

    trentm committed Oct 10, 2012
    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)
        * * *
Commits on Oct 9, 2012
  1. prep for future dev

    trentm committed Oct 9, 2012
  2. prepare for 0.14.1 release

    trentm committed Oct 9, 2012
  3. [issue #44] Fix the default `bunyan` CLI output of a `res.body` that …

    trentm committed Oct 9, 2012
    …is an object instead of a string.
    
    See issue#38 for the same with `req.body`.
Commits on Sep 10, 2012
  1. clarify log level best practices

    trentm committed Sep 10, 2012
  2. prep for future dev

    trentm committed Sep 10, 2012
  3. prepare for 0.14.0 release

    trentm committed Sep 10, 2012
  4. Merge pull request #41 from isaacs/master

    trentm committed Sep 10, 2012
    JSON.stringify safely
  5. JSON.stringify safely

    isaacs committed Sep 10, 2012
Commits on Aug 30, 2012
  1. prep for future dev

    trentm committed Aug 30, 2012
  2. prepare for 0.13.5 release

    trentm committed Aug 30, 2012
  3. [issue #39] Fix a bug with `client_req` handling in the default outpu…

    trentm committed Aug 30, 2012
    …t of the `bunyan` CLI.
Commits on Aug 29, 2012
Commits on Aug 28, 2012
  1. prep for future dev

    trentm committed Aug 28, 2012
  2. prepare for 0.13.4 release

    trentm committed Aug 28, 2012
  3. [issue #38] Fix the default `bunyan` CLI output of a `req.body` that …

    trentm committed Aug 28, 2012
    …is an object instead of a string.
Commits on Aug 24, 2012
  1. prep for future dev

    trentm committed Aug 24, 2012
  2. prepare for 0.13.3 release

    trentm committed Aug 24, 2012
  3. Export `bunyan.resolveLevel(NAME-OR-NUM)` to resolve a level name or …

    trentm committed Aug 24, 2012
    …number to its log level number value
Commits on Aug 22, 2012
  1. prep for future dev

    trentm committed Aug 22, 2012
  2. prepare for 0.13.2 release

    trentm committed Aug 22, 2012
  3. [issue #35] Ensure that an accidental `log.info(BUFFER)`, where BUFFE…

    trentm committed Aug 22, 2012
    …R is a node.js Buffer object, doesn't blow up.