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

Error: unexpected end of file at Zlib._handle.onerror #379

Closed
davenewza opened this issue Apr 7, 2016 · 6 comments
Closed

Error: unexpected end of file at Zlib._handle.onerror #379

davenewza opened this issue Apr 7, 2016 · 6 comments

Comments

@davenewza
Copy link

Running newman 2.0.6 on our build is now throwing the following error:

RequestError: [3da18a82-79ca-abd8-20e5-390b4e6affd8] 'Some Action' terminated. Complete error:
Error: unexpected end of file
at Zlib._handle.onerror (zlib.js:363:17)
× Is 401
Finished running Newman tests.

The collection is built using Postman 4.1.3. The collection runs perfectly fine in the Postman Collection Runner.

It's happening on a few items in our collection. This is one of them:

{
    "id": "f6c21354-80f0-ddd2-8782-fe9ff7331dde",
    "headers": "Content-Type: application/json\nAccept: application/json\n",
    "url": "{{Url}}/something",
    "preRequestScript": "",
    "pathVariables": {},
    "method": "GET",
    "data": [ ],
    "dataMode": "params",
    "version": 2,
    "tests": "tests[\"Is 401\"] = responseCode.code === 401;",
    "currentHelper": "normal",
    "helperAttributes": {},
    "time": 1449121531396,
    "name": "Some Action",
    "description": "",
    "collectionId": "0d31daa7-e3ae-094b-4ff5-920ca7683748",
    "responses": []
},

I have tried replacing it but to no avail.

@davenewza
Copy link
Author

This seems to be happening on around half of our requests out of the blue.

@czardoz
Copy link
Contributor

czardoz commented Apr 7, 2016

@davenewza, what Node version are you using?

@davenewza
Copy link
Author

@czardoz v5.10.1

@czardoz
Copy link
Contributor

czardoz commented Apr 8, 2016

Ah, looks like a duplicate of #319

  1. Are you able to consistently reproduce this issue?
  2. Do you run into this with Node v4.x as well?

@davenewza
Copy link
Author

  1. Yes, it consistently fails on specific requests.
  2. Just tested this and it runs fine on Node v4.x. Will have to downgrade (thanks)

@czardoz
Copy link
Contributor

czardoz commented Apr 18, 2016

Fixed on develop, will be available in the next release.

@czardoz czardoz closed this as completed Apr 18, 2016
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