Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sync api does not work #20

Open
stephg opened this issue Jun 27, 2016 · 2 comments
Open

sync api does not work #20

stephg opened this issue Jun 27, 2016 · 2 comments

Comments

@stephg
Copy link

stephg commented Jun 27, 2016

Whenever i call sync methods which use zlibBufferSync(), I get:

# zlib (zlibBufferSync) elipses.txt 16384 {"level":6,"windowBits":15,"memLevel":8,"strategy":0} DeflateRaw -> InflateRaw
not ok 82 Error: buffer error:
  ---
    operator: error
    expected: undefined
    actual:   { [Error: buffer error: ] errno: -5, code: 'Z_BUF_ERROR' }
    stack:
      Error: buffer error:
        at Zlib._binding.onerror (/Users/stephg/Development/checkpad/browserify-zlib/src/index.js:364:17)
        at Zlib._error (/Users/stephg/Development/checkpad/browserify-zlib/src/binding.js:229:8)
        at Zlib._write (/Users/stephg/Development/checkpad/browserify-zlib/src/binding.js:187:10)
        at Zlib.writeSync (/Users/stephg/Development/checkpad/browserify-zlib/src/binding.js:136:15)
        at InflateRaw.Zlib._processChunk (/Users/stephg/Development/checkpad/browserify-zlib/src/index.js:520:31)
        at Object.zlibBufferSync (/Users/stephg/Development/checkpad/browserify-zlib/src/index.js:235:17)
        at Test.<anonymous> (/Users/stephg/Development/checkpad/browserify-zlib/test/test-zlib.js:218:37)
        at Test.bound [as _cb] (/Users/stephg/Development/checkpad/browserify-zlib/node_modules/tape/lib/test.js:60:32)
        at Test.run (/Users/stephg/Development/checkpad/browserify-zlib/node_modules/tape/lib/test.js:74:14)
        at Test.bound [as run] (/Users/stephg/Development/checkpad/browserify-zlib/node_modules/tape/lib/test.js:60:32)
  ...

This is the test:
factisresearch@734fbab

@rbuels
Copy link

rbuels commented Aug 30, 2018

Is this still an issue? #18 claims that this was fixed by its merge.

@stephg
Copy link
Author

stephg commented Sep 3, 2018

Yes, looks like this is resolved by #18.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants