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

Trying to download large email (>5MB) throws when options http2: true #3109

Open
lopezvit opened this issue Nov 14, 2022 · 3 comments
Open
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@lopezvit
Copy link

Environment details

  • OS: Linux / Macos
  • Node.js version: v18.10.0
  • npm version: 8.19.2
  • googleapis version: 105/109.0.1

Steps to reproduce

  1. Get a large email from Google API with the options {http2: false}
  2. The function returns the following error:
Could not download email 17d03869ffcd2de1 Error: unexpected end of file
    at Zlib.zlibOnError [as onerror] (node:zlib:189:17)
    at Zlib.callbackTrampoline (node:internal/async_hooks:130:17) {
  errno: -5,
  code: 'Z_BUF_ERROR'
}

Making the same request using the Try this API

Making the same request with the {http2: false} option works as well.

Possibly related with:
#3108

@lopezvit lopezvit added priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Nov 14, 2022
@wdanilo
Copy link

wdanilo commented Jan 8, 2024

I have also observed that. As http2 should be used now instead of batch calls, this is pretty critical thing.

@transitive-bullshit
Copy link

In your steps to reproduce, I think you mean: {http2: true}

@lopezvit
Copy link
Author

yeah @transitive-bullshit , of course, in the steps to reproduce it should be the way you are describing it. I just meant, that I tried with {http2: false} and then it worked.

Hard to believe that is about the be the 2 year anniversary of this issue, and there is not answer.

Please, if any of you find that you are having the same issue, give a thumb's up 👍 as a reaction to the original post, so maybe it would be taken more into account by the developer team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

3 participants