-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Occasional Sync input too long
error response ?
#525
Comments
If the issue still persists, please file it here. Thank you. |
kweinmeister
pushed a commit
that referenced
this issue
Nov 18, 2022
🤖 I have created a release \*beep\* \*boop\* --- ### [3.2.3](https://www.github.com/googleapis/nodejs-text-to-speech/compare/v3.2.2...v3.2.3) (2021-06-23) ### Bug Fixes * make request optional in all cases ([#525](https://www.github.com/googleapis/nodejs-text-to-speech/issues/525)) ([256f21b](https://www.github.com/googleapis/nodejs-text-to-speech/commit/256f21bada718586549f07327be2509c79da3912)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
i'm having issues with nodejs client.
I'm using
node v8.8.1
and"@google-cloud/speech": "^0.11.0"
Sometimes I get:
For the same file, the request 3s later returns success:
I'm using this method to transcribe an audio:
I have a retry delay and total count of max 3 retries.
There is no pattern. Sometimes i get success on second request [ retry ], sometimes all three retires fail.
Files are correctly encoded and not longer than 60s. Which above debug messages prove.
I'm trying to figure out the issue for a while now and can't reproduce it or pinpoint the reason. It happens on some occasions. Google console states that around 40% of requests are failing in my case.
Any clue why may this be happening?
Thanx in advance,
Best
The text was updated successfully, but these errors were encountered: