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

Operations hanging indefinitely #465

Closed
callmehiphop opened this issue Apr 10, 2019 · 6 comments
Closed

Operations hanging indefinitely #465

callmehiphop opened this issue Apr 10, 2019 · 6 comments
Assignees
Labels
needs more info This issue needs more information from the customer to proceed. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. 🚨 This issue needs some love. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@callmehiphop
Copy link
Contributor

While trying to debug googleapis/nodejs-speech#330, I ran into a scenario where the operation would finish but it did not contain any results or errors, causing the polling to go on indefinitely, which made my process hang.

@callmehiphop callmehiphop added the type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. label Apr 10, 2019
@yoshi-automation yoshi-automation added the triage me I really want to be triaged. label Apr 11, 2019
@vam-google vam-google added the priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. label Apr 15, 2019
@yoshi-automation yoshi-automation added 🚨 This issue needs some love. and removed triage me I really want to be triaged. 🚨 This issue needs some love. labels Apr 15, 2019
@yoshi-automation yoshi-automation added 🚨 This issue needs some love. and removed 🚨 This issue needs some love. labels Apr 25, 2019
@yoshi-automation yoshi-automation added 🚨 This issue needs some love. and removed 🚨 This issue needs some love. labels May 5, 2019
@evaogbe
Copy link
Contributor

evaogbe commented May 13, 2019

@alexander-fenster Any updates?

@alexander-fenster
Copy link
Contributor

@eoogbe We have an internal issue tracking this Speech behavior (which is against the spec), but this issue should be closed by #436 which addresses this specific problem. I wonder if an old gax was used here - if not, it should be debugged further.

@alexander-fenster
Copy link
Contributor

@callmehiphop Can I ask you to double check if the code you were testing used gax that included #436? The original problem happens if the input file is silent or does not contain any speech to transcribe.

@bcoe bcoe added the needs more info This issue needs more information from the customer to proceed. label May 14, 2019
@JustinBeckwith JustinBeckwith added the 🚨 This issue needs some love. label May 20, 2019
@vchudnov-g
Copy link

@alexander-fenster Any updates?

@JustinBeckwith
Copy link
Contributor

@callmehiphop nudges

@callmehiphop
Copy link
Contributor Author

The issue that I referenced earlier seems to be closed now, so I'm going to assume that this is fixed. If it re-surfaces then I'll re-open this. Thanks all!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more info This issue needs more information from the customer to proceed. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. 🚨 This issue needs some love. 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

8 participants