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

Error: Value for field responseText is too long #8

Open
Fi1osof opened this issue Jun 13, 2018 · 2 comments
Open

Error: Value for field responseText is too long #8

Fi1osof opened this issue Jun 13, 2018 · 2 comments

Comments

@Fi1osof
Copy link

Fi1osof commented Jun 13, 2018

Trying set record value string ~1.5 Mbytes. Schema field type String.

type Queue {
  id: ID! @unique
  responseText: String
  ...
}

Database column type mediumtext | utf8mb4_unicode_ci (tryed set to longtext too).

Got error.

Error: Value for field responseText is too long.
    at BatchedGraphQLClient.<anonymous> (/...../server/node_modules/http-link-dataloader/src/BatchedGraphQLClient.ts:68:15)
    at step (/...../server/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:40:23)
    at Object.next (/...../server/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:21:53)
    at fulfilled (/...../server/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:12:58)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:182:7)

UPD: response length 1196808

@andreylh
Copy link

Same here, is anyone working on this?

@kgoggin
Copy link

kgoggin commented Apr 8, 2019

For anyone else who lands here... I initially had the field I got this error on defined as an ID! @unique, which I'd added to an existing data type with a dedicated id field already. After getting the error, I figured maybe it had to do with using ID, so I changed it to a String... still got the error. But then I completely deleted and re-deployed my Prisma service, (creating everything from scratch) and it started working fine.

Obviously deleting and redeploying isn't a viable solution in many cases (I'm lucky that the DB I was working on was still new) but maybe that'll help someone triage this or at least provide a work-around.

Oh, and I'm fairly certain the issue isn't with this library itself, but with the underlying Prisma code that's running on the Prisma server... this lib just shows up in the stacktrace because it's the one making the request to the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants