Stéphan Kochen
602c0c315c
Upgrade to dtrace-provider 0.6.
...
For io.js 3.x support.
2015-09-04 21:29:03 +02:00
Trent Mick
3be145a72c
drop 0.8 support; test with iojs3.0 (tho it is broken)
2015-08-16 17:51:30 -07:00
Trent Mick
930ce61533
prep for future dev
2015-06-07 11:07:49 -07:00
Trent Mick
5d666f49f1
update tests to run against some io.js versions. Minor test case fix for io.js slight diff to 0.12.
2015-06-07 11:06:50 -07:00
Stéphan Kochen
3f8ff80c8c
Upgrade to dtrace-provider 0.5.
...
Fixes #259 . Fixes #258 .
2015-06-07 11:03:50 -07:00
Trent Mick
15f2bb1133
prep for future dev
2015-06-01 22:13:17 -07:00
Trent Mick
a5bc7911d3
prep for future dev
2015-04-12 22:18:52 -07:00
Trent Mick
2828e462aa
prep for future dev
2015-02-20 14:55:15 -08:00
Trent Mick
6cabaa9a0b
prep for future dev
2015-01-26 09:24:03 -08:00
Rui Marinho
df5044d4dc
Update dtrace-provider@0.4.0
...
Adds io.js support.
Closes #212 .
2015-01-24 00:21:50 +00:00
Trent Mick
ffd9903d74
prep for future dev
2015-01-18 23:29:43 -08:00
Trent Mick
64b8fd1004
test cases for #182 , style tweaks, changelog, etc.
2015-01-18 23:27:28 -08:00
Martin Gausby
c0ca774238
Defend against throwing defined props in stringify
...
If an object has a defined property, that is enumerable, and this
property throws an error, it will make JSON stringify throw an
error, and potentially bring down the program.
The solution so far is to try-catch with the usual json stringifyer,
that guards against circular references. If this throws an error
we will attempt to guard against defined properties; and return
[Throws] if a property throws an error when accesed.
The following examples illustrate the problem:
```js
var obj = {};
obj.__defineGetter__('foo', function() { throw new Error('ouch!'); });
JSON.stringify(obj.foo); // error thrown
```
And using `Object.defineProperty`:
```js
var obj = {};
Object.defineProperty(obj, 'foo', {
get: function() { throw new Error('ouch!'); }
enumerable: true // enumerable is false by default
});
JSON.stringify(obj.foo); // error thrown
```
The cases we have seen in production is third party modules that
has enumerable getters that try to access properties on undefined
objects.
Fixes #182 .
2015-01-18 23:27:06 -08:00
Trent Mick
bed6fbfb66
prep for future dev
2015-01-17 22:05:16 -08:00
Trent Mick
b975c3a9f8
prep for future dev
2015-01-17 13:34:33 -08:00
Trent Mick
28e52193c6
meta data prepping for release
2015-01-16 23:02:29 -08:00
Trent Mick
783b1c4e39
prep for future dev
2015-01-15 22:20:21 -08:00
Trent Mick
79fc7178bd
prep for future dev
2014-11-17 21:46:54 -08:00
Trent Mick
48a903c040
prep for future dev
2014-11-13 23:15:55 -08:00
Trent Mick
e43a1a405f
prep for future dev
2014-10-25 21:06:13 -07:00
Trent Mick
603ce3c18b
Get at least dtrace-provider 0.3.1 for optionalDependencies
...
...to get a fix for install with decoupled npm (e.g. with homebrew's
node and npm).
Fixes #178 #181 .
2014-10-25 21:05:12 -07:00
Trent Mick
04de162a02
prep for future dev
2014-10-17 14:34:49 -07:00
Trent Mick
6fc941c9b4
Restore dtrace-provider in optionalDependencies
...
dtrace-provider v0.3.0 fixes build issues of yore. This fixes things
for node 0.11/0.12 usage.
Fixes #157
2014-10-15 22:18:11 -07:00
Trent Mick
5598700713
prep for future dev
2014-09-27 21:50:14 -07:00
Trent Mick
bd149b924b
prep for future dev
2014-09-27 21:26:15 -07:00
Trent Mick
b9f347b757
prep for future dev
2014-09-27 21:08:53 -07:00
Trent Mick
9c150d9c6e
prep for future dev
2014-09-21 21:21:06 -07:00
Trent Mick
414f33563d
browserify support, bump ver to 1.1.0
2014-09-21 21:20:43 -07:00
Trent Mick
cb703ef474
prep for future dev
2014-08-25 00:51:14 -07:00
Trent Mick
76bc7acca4
prep for future dev
2014-08-01 16:01:01 -07:00
Trent Mick
660b706479
doc new -c CODE; drop dtrace-provider as optionalDependency ( fixes #135 ); add 'bunyan -0' shortcut
2014-08-01 15:57:48 -07:00
Trent Mick
865cec6a6d
prep for future dev
2014-05-31 23:00:25 -07:00
Trent Mick
67b8bab6c9
prep for future dev
2014-05-30 21:00:24 -07:00
Trent Mick
d305801472
[issue #139 ] Fix bunyan
crash on a log record with res.header
that is an object.
2014-05-29 00:13:01 -07:00
Trent Mick
fc0150f9fb
[issue #85 ] Ensure logging a non-object/non-string doesn't throw
2014-05-28 23:24:57 -07:00
Trent Mick
9f3ef6b42a
prep for future dev
2014-04-10 17:00:33 -07:00
Trent Mick
5b9da22e85
prep for future dev
2014-04-03 16:02:43 -07:00
Trent Mick
a689ca171e
issue #128 : Update 'mv' optional dep to latest.
2014-03-19 09:11:34 -07:00
Trent Mick
0322832326
prep for future dev
2013-11-25 23:47:24 -08:00
Trent Mick
06ade787dc
prep for future dev
2013-10-11 13:17:14 -07:00
Trent Mick
eac13c08cc
issue #104 : log.reopenFileStreams()
convenience method to be used with external log rotation.
2013-10-11 13:16:29 -07:00
Trent Mick
27b679f243
prep for future dev
2013-07-02 16:44:16 -07:00
Trent Mick
8f7aff09b2
prep for future dev
2013-05-21 17:31:09 -07:00
Trent Mick
45dce561ec
prep for future dev
2013-05-17 02:12:30 -07:00
Trent Mick
b5e3bd290c
prep for future dev
2013-04-04 17:02:29 -07:00
Trent Mick
6841b8c184
prep for future dev
2013-04-01 21:00:54 -07:00
Trent Mick
3a9859365e
call this 0.21
2013-04-01 17:22:53 -07:00
Trent Mick
2d2d39d1a7
prep for future dev
2013-03-15 11:27:00 -07:00
Trent Mick
1a8be0c1e6
OS-2030, smartos-live #184 : fix serializer bug added in bunyan 0.18.3
2013-03-15 11:25:56 -07:00
Sven Ambros
65e1e8217c
Update package.json
...
The reason updating mv is, that mv v0.0.4 does not support the current stable version of v0.10.0.
2013-03-12 11:33:49 +01:00