Google-cloud-python: Speech: Obscure encoding error message

[chemelnucfin]

Using the wrong encoding for the file results in an error that does not easily point to the right cause.

self._exceptiongoogle.api_core.exceptions.GoogleAPICallError:
None Unexpected state: Long-running operation had neither response nor
error set.

See
#4885 for background info.

[chemelnucfin]

@jonparrott Is there anything we can do on our end or would this a backend issue? Who would I talk to for that?

[theacodes]

@jerjou maybe?

[HaHatake]

I also encountered the error "Long-running operation had neither response nor error set"
Is this session timeout ?

[tseaver]

google.api_core.operation.Operation._set_result_from_operation is raising this error because its self._operation.done flag is already true, but neither error nor response is set. This is a bug in the backend: the API docs for Operation state:

Union field result. The operation result, which can be either an error or a valid response. If done == false, neither error nor response is set. If done == true, exactly one of error or response is set. result can be only one of the following:
error | Status The error result of the operation in case of failure or cancellation.

response | Any The normal response of the operation in case of success. If the original method returns no data on success, such as Delete, the response is google.protobuf.Empty. If the original method is standard Get/Create/Update, the response should be the resource. For other methods, the response should have the type XxxResponse, where Xxx is the original method name. For example, if the original method name is TakeSnapshot(), the inferred response type is TakeSnapshotResponse.

@theacodes, @crwilcox please loop in the appropriate PoC for the Speech API team.

[tseaver]

@theacodes, @crwilcox Who is our back-end PoC for the Speech API?

[jerjou]

I thought I fixed this. Is this still happening?

[tseaver]

@jerjou Was your fix in the back-end? I saw your first pass at it in PR #5406, but you closed it without a merge, noting:

Just to close the loop on this - turns out it was a server error.

[jerjou]

Oh - yes. It was.

[tseaver]

@jerjou Can we close this issue because that fix is deployed in production?

[jerjou]

Yup!

[tseaver]

W00t! Thanks, @jerjou .

[flavienbwk]

Issue is still active for the Google Cloud Speech API in Python (diarization).

[JOSEPHNAVIN]

Any update on this issue ?

[Napoleon-Black]

I faced the same problem. I'm using Python 3.7 and the latest versions of google-cloud-speech and
google-cloud-storage.

[JeffersonH44]

I'm also experiencing the same problem with python 3.5, 3.6 and 3.7, with the gcloud command it works.

also using any previous version of google-cloud-speech doesn't work, seems that's a backend error

[NikolayPogoreliy]

Yea!!! I have the same trouble with google-cloud-speech and
google-cloud-storage on Python3.6.
PS
@tseaver It's seems like no one care(((

[JeffersonH44]

for those who doesn't know, there's an issue in the issue tracker here:

https://issuetracker.google.com/issues/122732566

it seems that the problem is when speech doesn't detect anything on the audio that doesn't retrieve any "friendly" message