Hi everyone.
I'm having some trouble with the pri...
# orm-helps
Saul Nachman
09/03/2021, 6:19 AMHi everyone.
I'm having some trouble with the prisma client (I think) deploying to netlify with nextjs (with a supabase db). I'm able to write to the db but my queries are failings.
Help understanding the debugging tools here would also be helpful. Where is the best place to get some help?
r
Ryan
09/03/2021, 6:27 AM@Saul Nachman 👋
Are you getting any error message when it fails?
Try adding a
try/catchcatchRyan
09/03/2021, 6:28 AMHave a look at these links as well if it helps 🙂
http://pris.ly/d/debugging
http://pris.ly/d/logging
s
Saul Nachman
09/03/2021, 6:30 AMAlso got a "failed to fetch schema error" at one stage, though can't seem to get it again where I can see it.
Saul Nachman
09/03/2021, 6:30 AMThanks for the links.
Saul Nachman
09/03/2021, 6:31 AMI'll get to console logging once I understand better where the error is.
r
Ryan
09/03/2021, 6:32 AMIs introspection enabled on the GraphQL server?
s
Saul Nachman
09/03/2021, 6:33 AMI don't know. New to the stack. How would I check?
r
Ryan
09/03/2021, 6:33 AMHow did you initialise the GraphQL server in your code?
s
Saul Nachman
09/03/2021, 6:34 AMSaul Nachman
09/03/2021, 6:34 AM Copy code
import { ApolloServer } from "apollo-server-micro";r
Ryan
09/03/2021, 6:35 AMAfter the conxtext, you should get an option of
introspectiontrues
Saul Nachman
09/03/2021, 6:36 AMok lemme see
Saul Nachman
09/03/2021, 6:38 AMNot seeing it in type defs. Lemme check the docs
Saul Nachman
09/03/2021, 6:39 AMtracing and debug may be useful tho
Saul Nachman
09/03/2021, 6:40 AMintellisense completes introspection so lets use it
Saul Nachman
09/03/2021, 6:41 AMI'll say when it's built
Saul Nachman
09/03/2021, 6:53 AMNo changes that I can see. Just getting a 502 in console now
Saul Nachman
09/03/2021, 6:57 AM Copy code
8:45:48 AM: 2021-09-03T06:45:48.303Z undefined INFO Loaded env from .env
8:45:48 AM: 2021-09-03T06:45:48.700Z prisma:tryLoadEnv Environment variables not found at /var/task/.env
8:45:48 AM: 2021-09-03T06:45:48.701Z prisma:tryLoadEnv Environment variables not found at /var/task/.env
8:45:48 AM: 2021-09-03T06:45:48.701Z prisma:tryLoadEnv No Environment variables loaded
8:45:48 AM: 2021-09-03T06:45:48.702Z prisma:tryLoadEnv Environment variables not found at /var/task/.env
8:45:48 AM: 2021-09-03T06:45:48.702Z prisma:tryLoadEnv Environment variables not found at /var/task/.env
8:45:48 AM: 2021-09-03T06:45:48.702Z prisma:tryLoadEnv No Environment variables loaded
8:45:48 AM: 2021-09-03T06:45:48.704Z prisma:client clientVersion: 2.20.1
8:45:49 AM: 2021-09-03T06:45:48.837Z undefined WARN Warning: nexus-plugin-prisma@0.35.0 does not support @prisma/client@2.20.1. The supported range is: `2.23.x`. This could lead to undefined behaviors and bugs.
8:45:49 AM: 2021-09-03T06:45:49.260Z undefined ERROR (node:8) [DEP0131] DeprecationWarning: The legacy HTTP parser is deprecated.
8:45:49 AM: 7d826eb5 INFO [request] /api
8:45:49 AM: 7d826eb5 Duration: 61.10 ms Memory Usage: 126 MB Init Duration: 1186.53 ms 8:46:32 AM: 2021-09-03T06:46:32.688Z prisma:engine Search for Query Engine in /var/task/node_modules/.prisma/clientSaul Nachman
09/03/2021, 6:57 AMFunction logs. Might have something to do with it.
r
Ryan
09/03/2021, 6:58 AMThere should be more to the function logs.
s
Saul Nachman
09/03/2021, 6:59 AMJust stuff like this repeated over and over:
Copy code
8:55:50 AM: 90dd2a62 INFO [request] /api
8:55:50 AM: 90dd2a62 Duration: 5.43 ms Memory Usage: 131 MBSaul Nachman
09/03/2021, 7:03 AMWhat were you expecting from server introspection?
r
Ryan
09/03/2021, 7:04 AMThere should be some error related to either Prisma or GraphQL so that would make it easier to see what the issue is.
Ryan
09/03/2021, 7:04 AMDoes everything work fine locally?
s
Saul Nachman
09/03/2021, 7:05 AMYeah
Saul Nachman
09/03/2021, 7:05 AMI suspect there's something being lost from files or env vars in the move to functions
r
Ryan
09/03/2021, 7:07 AMWe have an example test here for Netlify with Prisma. Could you compare that with your setup and check?
s
Saul Nachman
09/03/2021, 7:07 AMSure will do. This is being mediated by the next deploy, so that might be in the way
💯 1
Saul Nachman
09/03/2021, 8:07 AMFwiw. Just trying to get logs atm
Saul Nachman
09/03/2021, 8:28 AM Copy code
10:23:16 AM: 2021-09-03T08:23:16.472Z prisma:getGenerators {
10:23:16 AM: neededVersions: [Object: null prototype] {
10:23:16 AM: '60ba6551f29b17d7d6ce479e5733c70d9c00860e': { engines: [Array], binaryTargets: [] }
10:23:16 AM: }
10:23:16 AM: }
10:23:16 AM: 2021-09-03T08:23:16.510Z prisma:getGenerators {
10:23:16 AM: generatorBinaryPaths: {
10:23:16 AM: queryEngine: {
10:23:16 AM: 'debian-openssl-1.1.x': '/opt/build/repo/node_modules/prisma/query-engine-debian-openssl-1.1.x',
10:23:16 AM: 'rhel-openssl-1.0.x': '/opt/build/repo/node_modules/prisma/query-engine-rhel-openssl-1.0.x'
10:23:16 AM: }
10:23:16 AM: }
10:23:16 AM: }Saul Nachman
09/03/2021, 8:28 AMGetting this output on build logs
Saul Nachman
09/03/2021, 1:40 PMIt turned out to have been an issue with the netlify process. I have it running fine on vercel
🤔 1
r
Ryan
09/03/2021, 1:44 PMOhh, that’s strange. No luck with logs, as in no error message regarding the 502?
s
Saul Nachman
09/03/2021, 1:45 PMcouldn't get to the bottom of it
Saul Nachman
09/03/2021, 1:45 PMsame deployment on vercel
Saul Nachman
09/03/2021, 1:46 PMpretty sure it was re the apollo server
r
Ryan
09/03/2021, 1:47 PMSeems like it.
6 Views