Error: 13 INTERNAL: Received RST_STREAM with code 2
See original GitHub issueYo, I’ve been having this random error lately, and I have no idea why.
Error: 13 INTERNAL: Received RST_STREAM with code 2
details: ‘Received RST_STREAM with code 2’, metadata: Metadata { internalRepr: Map {}, options: {} }, note: 'Exception occurred in retry method that was not classified as transient
Code:
const vision = require('@google-cloud/vision');
const client = new vision.ImageAnnotatorClient({projectId: "...", keyFilename: "....json"});
...
const [result] = await gclient.textDetection(image);
const texts = result.fullTextAnnotation;
console.log(texts)
The image is a remote url.
And thanks in advance.
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (3 by maintainers)
Top Results From Across the Web
13 INTERNAL: Received RST_STREAM with code 2 triggered ...
i reuse a connection for all request , sometime seems connection will disconnect when idle for a long times (client error: read ECONNRESET), ......
Read more >Error: 13 INTERNAL: Received RST_STREAM with code 2 ...
"Protocol error" generally indicates that the client got something other than a valid HTTP/2 response from the server or proxy that it was ......
Read more >Received RST_STREAM with code 2 (Internal server error)
Hi, I've received another server-generated grpc error on my hosted slash.dgraph.io instance. This time it's different:
Read more >grpc/grpc - Gitter
Anyone have experience w mutual TLS in node.js? I'm getting Received RST_STREAM with code 2 (Internal server error) which I think means auth...
Read more >Received RST_STREAM with error code 2 - Google Groups
You received this message because you are subscribed to the Google Groups "UniMRCP" group. To unsubscribe from this group and stop receiving emails...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@alexander-fenster Still getting these errors mate.
This issue is still occurring when processing large volumes of images. We’re getting the original error it’s only started happening today prior to the upgrade we were running
vision ^1.9.0
as well as
Bump because I’m also having this issue. Similar to @david-taggun I’m getting this error when sending larger quantities of images (not that crazy or anything)
Seems to be happening whenever I send around 30+ images within a couple minutes. Whenever I’m not getting the error it is taking painfully long to get a response (like 2-3 minutes for 8-10 images). Also, the images aren’t crazy intricate or anything. They’re fairly basic images such as a simple picture of a bus with nothing else.