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

Google cloud translate api does not honour request timeout #1410

Closed
urjitbhatia opened this issue Jan 19, 2023 · 5 comments
Closed

Google cloud translate api does not honour request timeout #1410

urjitbhatia opened this issue Jan 19, 2023 · 5 comments
Assignees
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

@urjitbhatia
Copy link

Yes, see the PR here: googleapis/google-cloud-node#3849
Google cloud translate api does not honour the request timeout in the patched request code.

  • OS: ubuntu
  • Node.js version: 18
  • npm version: (Yarn 1.22.4)
  • google-gax version: 3.5.2

Steps to reproduce

  1. Create a translate client.
  2. Set a request timeout
  3. Point request to a dummy server that takes long or set a really small timeout to test
  4. Request continues beyond the timeout and doesn't abort

Making sure to follow these steps will guarantee the quickest resolution possible.

Thanks!

@urjitbhatia urjitbhatia 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 Jan 19, 2023
@dbellizzi
Copy link

For more context, the bug is seen in the v2 translate client, we haven't verified whether the v3 client has this issue or not.

@bcoe
Copy link
Contributor

bcoe commented Jan 31, 2023

CC: @leahecole, this may be adjacent to the retry work you're doing.

@leahecole
Copy link
Contributor

I was just poking around gax issues again and at first glance, I'm not sure this is adjacent to the gax work because the v2 code linked does not call gax at all.

@alexander-fenster
Copy link
Contributor

Just to give you some details - Translate is a combined library, v2 is handwritten and v3* are GAPIC generated. Any issues with retries in v2 are likely coming from retry-request via @google-cloud/common (likely).

@leahecole
Copy link
Contributor

Closing this as obsolete - if this is still an issue, Alex's previous comment about it coming from @google-cloud/common is right. If the v3 client is having an issue, feel free to lmk and I can upgrade it to use gax native retries instead.

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

5 participants