anyone seeing `Server response was missing for query null ` Prisma #prisma-whats-new

anyone seeing `Server response was missing for que...

jjaybrown98

01/30/2018, 9:56 PM

anyone seeing

Server response was missing for query'null'

errors with prisma? I don't believe I'm making a high freq of requests

nilan

01/30/2018, 10:13 PM

hey there, can you reliably reproduce this error message?

jjaybrown98

01/30/2018, 10:31 PM

yes, when running against 100 or so requests in a map

nilan

01/30/2018, 10:31 PM

are you running that locally or against a public cluster?

jjaybrown98

01/30/2018, 10:32 PM

happens in both

nilan

01/30/2018, 10:33 PM

got it - when you say requests in a map, what do you mean?

jjaybrown98

01/30/2018, 10:34 PM

Promise.all( map((article) => { insert(article) }) )

jjaybrown98

01/30/2018, 10:35 PM

that's omitted some of the details, but it's so I proceed once 100 articles in a batch have been created

nilan

01/30/2018, 10:36 PM

ah, that definitely sounds like the endpoint doesn't handle the many HTTP requests that hit it in a short duration correctly. Does the response come from Prisma directly, or from GraphQL Yoga?

jjaybrown98

01/30/2018, 10:37 PM

hard to tell, just has that message for operationNamed: null

jjaybrown98

01/30/2018, 10:37 PM

side question, how do you name an operation if you're using binding?

nilan

01/30/2018, 10:42 PM

I created this bug report, will further investigate: https://github.com/graphcool/prisma/issues/1788

veksen

01/30/2018, 10:44 PM

the buddy I'm working on had the same issue (

Server response was missing for query'null'

, with a repo that worked on my end -- so I can rule out something with the code itself. Seemed to be an issue with his endpoint

jjaybrown98

01/30/2018, 10:44 PM

it could be server resources, @nilan for the public clusters what's the resource scaled to?

veksen

01/30/2018, 10:45 PM

trace if that helps:

Copy code

[Network error]: Error: Server response was missing for query 'null'.
Error: Server response was missing for query 'null'.
    at Object.checkResultAndHandleErrors (C:\novartem\<http://novartem.com|novartem.com>\new_marketplace_staging\marketplace-backend\node_modules\graphql-tools\dist\stitching\errors.js:69:36)
    at Object.<anonymous> (C:\novartem\<http://novartem.com|novartem.com>\new_marketplace_staging\marketplace-backend\node_modules\graphql-tools\dist\stitching\delegateToSchema.js:92:52)
    at step (C:\novartem\<http://novartem.com|novartem.com>\new_marketplace_staging\marketplace-backend\node_modules\graphql-tools\dist\stitching\delegateToSchema.js:40:23)
    at Object.next (C:\novartem\<http://novartem.com|novartem.com>\new_marketplace_staging\marketplace-backend\node_modules\graphql-tools\dist\stitching\delegateToSchema.js:21:53)
    at fulfilled (C:\novartem\<http://novartem.com|novartem.com>\new_marketplace_staging\marketplace-backend\node_modules\graphql-tools\dist\stitching\delegateToSchema.js:12:58)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:160:7)

nilan

01/30/2018, 10:46 PM

@veksen, I had that too, but it's unrelated.

nilan

01/30/2018, 10:47 PM

Looks like this error message is thrown by

graphql-tools

, and there are many different causes for it

nilan

01/30/2018, 10:48 PM

@jjaybrown98 we'll share more about the cluster resources soon, what's for sure is that they have a rate limiting in place and I wonder if something goes wrong with the request queue

veksen

01/30/2018, 10:49 PM

I see - I'm not sure how much control you have on that with Prisma, and I know you're currently looking for feedback and fixing some bugs -- don't mean to hijack threads. Where should feedback be sent?

nilan

01/30/2018, 10:51 PM

thanks so much @veksen, depending on the kind of feedback, https://www.graph.cool/forum/c/feedback or https://github.com/graphcool/prisma 🙂

👍 1

2 Views

Open in Slack

Previous Next