-
Notifications
You must be signed in to change notification settings - Fork 165
creationix/jsonparse bumped to 0.0.5 #27
Comments
cool, fixed in 0.4.4 |
tests are passing for me, are you sure you are running tests on master? |
Thought I was, just did a clone which would have put me on the master branch-- not at the keys right now but ill check again later when I am and let you know what I see. On Mar 14, 2013, at 5:46 PM, Dominic Tarr [email protected] wrote:
|
Ok so I get an error -- v0.8.9⚡ node -e "console.log(process.versions)"
{ http_parser: '1.0',
node: '0.8.9',
v8: '3.11.10.22',
ares: '1.7.5-DEV',
uv: '0.8',
zlib: '1.2.3',
openssl: '1.0.0f' } jlank in ~/tmp/JSONStream on master*
⚡ npm test
> JSONStream@0.4.3 test /Users/johnlancaster/tmp/JSONStream
> set -e; for t in test/*.js; do echo '***' $t '***'; node $t; done
*** test/bool.js ***
PASSED
*** test/destroy_missing.js ***
PASSED
*** test/empty.js ***
PASSED
*** test/fn.js ***
PASSED
*** test/multiple_objects.js ***
END
*** test/multiple_objects_error.js ***
[Error: Unexpected RIGHT_BRACE("}") in state VALUE]
*** test/parsejson.js ***
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
correct 0.9337508901953697
parsed 0.9337508901953697
parsed [ 0.9337508901953697 ]
*** test/stringify.js ***
PASSED
*** test/stringify_object.js ***
PASSED
*** test/test.js ***
PASSED
*** test/test2.js ***
PASSED
*** test/two-ways.js ***
PASSED v0.10.0⚡ node -e "console.log(process.versions)"
{ http_parser: '1.0',
node: '0.10.0',
v8: '3.14.5.8',
ares: '1.9.0-DEV',
uv: '0.9',
zlib: '1.2.3',
openssl: '1.0.1e' } jlank in ~/tmp/JSONStream on master*
⚡ npm test
> JSONStream@0.4.3 test /Users/johnlancaster/tmp/JSONStream
> set -e; for t in test/*.js; do echo '***' $t '***'; node $t; done
*** test/bool.js ***
PASSED
*** test/destroy_missing.js *** freezes there |
that is not an error in the 0.8 version, if it's an error, the test That is an error on the 0.10 test, though. Streams2 changes the meaning of |
Also, this now uses through internally, so it uses backpressure correctly, and buffers. |
Hey @dominictarr,
Thanks for the great module! When I was using it I discovered an underlying bug in jsonparse relating to utf8 encoding, and patched it. It has landed in 0.0.5. I pulled down JSONStream and updated the package.json to 0.0.5 and ran
npm test
, there is one error[Error: Unexpected RIGHT_BRACE("}") in state VALUE]
, but that is also present withjsonparse
0.0.4, so I think it's safe to update to 0.0.5. If you want I can send a PR for this.Thanks!
The text was updated successfully, but these errors were encountered: