-
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
How to change Client GRPC deadline? #283
Comments
@jmuk How would one increase the deadline? |
The autogen layer can customize the deadline through the Which method are you using? I'm wild-guessing that |
Something like this would work: const v1beta1 = require('@google-cloud/speech').v1beta1();
const speech = v1beta1.speechClient();
const request = {
audio: {
uri: 'gs://my-bucket/filename.raw'
},
config: {
encoding: 'LINEAR16',
sampleRate: 16000
}
};
const options = {
longrunning: {
initialRetryDelayMillis: 100, , // Default
retryDelayMultiplier: 1.3, // Default
maxRetryDelayMillis: 60000, // Default
initialRpcTimeoutMillis: null, // Default
rpcTimeoutMultiplier: null, // Default
maxRpcTimeoutMillis: null, // Default
totalTimeoutMillis: 600000 // Default
}
};
speech.syncRecognize(request, options)
.then((results) => {
const transcription = results[0];
console.log(transcription);
}); |
@jmdobry Would this work with recognizeStream? |
I'm not sure the bi-directional streaming uses exponential backoff. @jmuk? |
@bloodcarter: const speech = require('@google-cloud')();
const stream = speech.createRecognizeStream(..., {timeout: 300});
... @jmdobry: bidi streaming does not use exponential backoff, but uses const v1beta1 = require('@google-cloud/speech').v1beta1();
const speech = v1beta1.speechClient();
// set the timeout to 300 seconds.
const stream = speech.streamingRecognize({timeout: 300});
stream.write(...);
... This should customize the timeout. |
* updated CHANGELOG.md [ci skip] * updated package.json [ci skip] * updated samples/package.json [ci skip]
* updated CHANGELOG.md [ci skip] * updated package.json [ci skip] * updated samples/package.json [ci skip]
…ssing samples (#283) * docs(samples): add OCR, form, quality, splitter and specialized processing samples * 🦉 Updates from OwlBot See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
…ssing samples (#283) * docs(samples): add OCR, form, quality, splitter and specialized processing samples * 🦉 Updates from OwlBot See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
…ssing samples (#283) * docs(samples): add OCR, form, quality, splitter and specialized processing samples * 🦉 Updates from OwlBot See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
fix(deps): update dependency nodemailer to v6 This PR contains the following updates: | Package | Type | Update | Change | References | |---|---|---|---|---| | nodemailer | dependencies | major | [`^5.0.0` -> `^6.0.0`](https://diff.intrinsic.com/nodemailer/5.1.1/6.0.0) | [homepage](https://nodemailer.com/), [source](https://github.com/nodemailer/nodemailer) | --- ### Release Notes <details> <summary>nodemailer/nodemailer</summary> ### [`v6.0.0`](https://github.com/nodemailer/nodemailer/blob/master/CHANGELOG.md#​600-2019-03-25) [Compare Source](https://github.com/nodemailer/nodemailer/compare/v5.1.1...v6.0.0) - SMTPConnection: use removeListener instead of removeAllListeners (xr0master) [ddc4af15] Using removeListener should fix memory leak with Node.js streams </details> --- ### Renovate configuration :date: **Schedule**: "after 9am and before 3pm" (UTC). :vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied. :recycle: **Rebasing**: Whenever PR is stale, or if you modify the PR title to begin with "`rebase!`". :no_bell: **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- renovate-rebase -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/marketplace/renovate). View repository job log [here](https://renovatebot.com/dashboard#googleapis/nodejs-compute). #283 automerged by dpebot
…ssing samples (#283) * docs(samples): add OCR, form, quality, splitter and specialized processing samples * 🦉 Updates from OwlBot See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
🤖 I have created a release \*beep\* \*boop\* --- ## [3.9.0](https://github.com/googleapis/nodejs-secret-manager/compare/v3.8.1...v3.9.0) (2021-07-30) ### Features * In Secret Manager, users can now use filter to customize the output of ListSecrets/ListSecretVersions calls ([#283](https://github.com/googleapis/nodejs-secret-manager/issues/283)) ([063691a](https://github.com/googleapis/nodejs-secret-manager/commit/063691a87291fab82037e9b444812dcf0724eb0c)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
fix(deps): update dependency nodemailer to v6 This PR contains the following updates: | Package | Type | Update | Change | References | |---|---|---|---|---| | nodemailer | dependencies | major | [`^5.0.0` -> `^6.0.0`](https://diff.intrinsic.com/nodemailer/5.1.1/6.0.0) | [homepage](https://nodemailer.com/), [source](https://github.com/nodemailer/nodemailer) | --- ### Release Notes <details> <summary>nodemailer/nodemailer</summary> ### [`v6.0.0`](https://github.com/nodemailer/nodemailer/blob/master/CHANGELOG.md#​600-2019-03-25) [Compare Source](https://github.com/nodemailer/nodemailer/compare/v5.1.1...v6.0.0) - SMTPConnection: use removeListener instead of removeAllListeners (xr0master) [ddc4af15] Using removeListener should fix memory leak with Node.js streams </details> --- ### Renovate configuration :date: **Schedule**: "after 9am and before 3pm" (UTC). :vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied. :recycle: **Rebasing**: Whenever PR is stale, or if you modify the PR title to begin with "`rebase!`". :no_bell: **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- renovate-rebase -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/marketplace/renovate). View repository job log [here](https://renovatebot.com/dashboard#googleapis/nodejs-compute). #283 automerged by dpebot
fix(deps): update dependency nodemailer to v6 This PR contains the following updates: | Package | Type | Update | Change | References | |---|---|---|---|---| | nodemailer | dependencies | major | [`^5.0.0` -> `^6.0.0`](https://diff.intrinsic.com/nodemailer/5.1.1/6.0.0) | [homepage](https://nodemailer.com/), [source](https://github.com/nodemailer/nodemailer) | --- ### Release Notes <details> <summary>nodemailer/nodemailer</summary> ### [`v6.0.0`](https://github.com/nodemailer/nodemailer/blob/master/CHANGELOG.md#​600-2019-03-25) [Compare Source](https://github.com/nodemailer/nodemailer/compare/v5.1.1...v6.0.0) - SMTPConnection: use removeListener instead of removeAllListeners (xr0master) [ddc4af15] Using removeListener should fix memory leak with Node.js streams </details> --- ### Renovate configuration :date: **Schedule**: "after 9am and before 3pm" (UTC). :vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied. :recycle: **Rebasing**: Whenever PR is stale, or if you modify the PR title to begin with "`rebase!`". :no_bell: **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- renovate-rebase -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/marketplace/renovate). View repository job log [here](https://renovatebot.com/dashboard#googleapis/nodejs-compute). #283 automerged by dpebot
I randomly receive this error while streaming data:
Client GRPC deadline too short. Should be at least: 3 * audio-duration + 5 seconds. Current deadline is: 59.699356980447192 second(s). Required at least: 60 second(s).
What should I do with that?
The text was updated successfully, but these errors were encountered: