Skip to content
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.

Malordered Data Received. Send exactly one config, followed by audio data. #170

Closed
stephenplusplus opened this issue Sep 14, 2018 · 4 comments
Assignees
Labels
api: speech Issues related to the googleapis/nodejs-speech API. 🚨 This issue needs some love. status: duplicate Duplicate. triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@stephenplusplus
Copy link
Contributor

Originally posted in #62 (comment)

I've updated to v2.1.0 and I'm getting the following error (error event in streamingRecognize() returned instance:

[3 INVALID_ARGUMENT: Malordered Data Received. Send exactly one config, followed by audio data.]

Would you be so kind to respond these questions,

  • How has the API changed for this error to happen?

  • Is v2.1.0 stable or beta?

In summary. I just would like to upgrade to the fixed version and make it work as before.

Thanks

@stephenplusplus stephenplusplus added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Sep 14, 2018
@stephenplusplus
Copy link
Contributor Author

@jmillan -- is this repo still the one that will reproduce this error?

@JustinBeckwith JustinBeckwith added the triage me I really want to be triaged. label Sep 15, 2018
@jmillan
Copy link

jmillan commented Sep 17, 2018

Hi,

@jmillan -- is this repo still the one that will reproduce this error?

Not in that repo.

Just run the tests of this (yes nodejs-speech) repo:

jmillan@Mac.local:~/src/nodejs-speech/samples (master)$ node recognize.js listen
Listening, press Ctrl+C to stop.
(node:45299) DeprecationWarning: grpc.load: Use the @grpc/proto-loader module with grpc.loadPackageDefinition instead
{ Error: 3 INVALID_ARGUMENT: Malordered Data Received. Send exactly one config, followed by audio data.
    at Object.exports.createStatusError (/Users/jmillan/src/nodejs-speech/samples/node_modules/grpc/src/common.js:87:15)
    at ClientDuplexStream._emitStatusIfDone (/Users/jmillan/src/nodejs-speech/samples/node_modules/grpc/src/client.js:235:26)
    at ClientDuplexStream._receiveStatus (/Users/jmillan/src/nodejs-speech/samples/node_modules/grpc/src/client.js:213:8)
    at Object.onReceiveStatus (/Users/jmillan/src/nodejs-speech/samples/node_modules/grpc/src/client_interceptors.js:1290:15)
    at InterceptingListener._callNext (/Users/jmillan/src/nodejs-speech/samples/node_modules/grpc/src/client_interceptors.js:564:42)
    at InterceptingListener.onReceiveStatus (/Users/jmillan/src/nodejs-speech/samples/node_modules/grpc/src/client_interceptors.js:614:8)
    at /Users/jmillan/src/nodejs-speech/samples/node_modules/grpc/src/client_interceptors.js:1110:18
  code: 3,
  metadata: Metadata { _internal_repr: {} },
  details: 'Malordered Data Received. Send exactly one config, followed by audio data.' }

@stephenplusplus stephenplusplus removed the triage me I really want to be triaged. label Sep 17, 2018
@JustinBeckwith JustinBeckwith added the triage me I really want to be triaged. label Sep 17, 2018
@jkwlui jkwlui removed the triage me I really want to be triaged. label Sep 17, 2018
@jkwlui
Copy link
Member

jkwlui commented Sep 17, 2018

Duplicate of #173

@jkwlui jkwlui marked this as a duplicate of #173 Sep 17, 2018
@JustinBeckwith JustinBeckwith added triage me I really want to be triaged. 🚨 This issue needs some love. status: duplicate Duplicate. labels Sep 17, 2018
@ghost ghost removed the priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. label Sep 21, 2018
@google-cloud-label-sync google-cloud-label-sync bot added the api: speech Issues related to the googleapis/nodejs-speech API. label Jan 31, 2020
@JustinBeckwith JustinBeckwith self-assigned this Feb 1, 2021
@RaphiePS
Copy link

RaphiePS commented Feb 4, 2021

Just to provide a little more context - I'm experiencing this both with my own code, and as a sanity check, with @vin-ni's Socket Playground here.

I'm able to use my credentials for other Speech requests. So it seems like I can rule out my code being bad (in this specific case, hah) and my auth being bad. Strange stuff.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api: speech Issues related to the googleapis/nodejs-speech API. 🚨 This issue needs some love. status: duplicate Duplicate. triage me I really want to be triaged. 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