Nexus-plugin-prisma: Invalid `photon.()` invocation
While trying to build an application backed by a serverless Apollo GraphQL instance, I encountered the following issue:
{
"errors": [
{
"message": "\nInvalid `photon.()` invocation in /var/task/src/node_modules/nexus-prisma/dist/builder.js:129:97\n\n\n\nundefined target=\"exit\" timestamp=\"2019-11-28T02:18:36.253Z\" fields={\"message\":\"127\"}",
"locations": [
{
"line": 2,
"column": 3
}
],
"path": [
"quizzes"
],
"extensions": {
"code": "INTERNAL_SERVER_ERROR",
"exception": {
"stacktrace": [
"Error: ",
"Invalid `photon.()` invocation in /var/task/src/node_modules/nexus-prisma/dist/builder.js:129:97",
"",
"",
"",
"undefined target=\"exit\" timestamp=\"2019-11-28T02:18:36.253Z\" fields={\"message\":\"127\"}",
" at PhotonFetcher.<anonymous> (/var/task/src/node_modules/@prisma/photon/index.js:54:27)",
" at Generator.throw (<anonymous>)",
" at rejected (/var/task/src/node_modules/@prisma/photon/index.js:6:65)",
" at <anonymous>"
]
}
}
}
],
"data": null
}
I executed the following query from here to get the aforementioned result:
{
quizzes {
id
}
}
The source code of the entire application is available from https://github.com/kripod/exigo, along with the corresponding build log here.
kripod
All 10 comments
I'm getting the same error.
Error:
Invalid `photon.()` invocation in /path/to/project/packages/server/node_modules/nexus-prisma/src/builder.ts:238:18
234 const photon = this.getPhoton(ctx)
235 assertPhotonInContext(photon)
236 return photon[mappedField.photonAccessor][
237 mappedField.operation
→ 238 ](args
undefined target="exit" timestamp="2019-12-04T16:44:27.839Z" fields={"message":"1"}
at PhotonFetcher.<anonymous> (/path/to/project/node_modules/@prisma/photon/index.js:54:27)
at Generator.throw (<anonymous>)
at rejected (/path/to/project/node_modules/@prisma/photon/index.js:6:65)
. ├── node_modules │ ├── @prisma │ │ ├── engine-core │ │ ├── fetch-engine │ │ ├── generator-helper │ │ ├── get-platform │ │ ├── photon │ │ └── sdk │ ├── nexus │ ├── nexus-prisma │ └── ... ├── lerna.json ├── package.json ├── packages │ ├── app │ │ ├── node_modules │ │ ├── package.json │ │ ├── src │ │ │ └──... │ │ ├── tsconfig.json │ │ └── tsconfig.paths.json │ ├── common │ │ ├── node_modules │ │ ├── package.json │ │ ├── src │ │ │ └──... │ │ ├── tsconfig.json │ │ └── tslint.json │ └── server │ ├── node_modules │ │ ├── @types │ │ │ └── nexus-typegen │ │ └── seed.ts │ ├── package.json │ ├── prisma │ │ ├── migrations │ │ │ ├── 20191128230530 │ │ │ │ ├── README.md │ │ │ │ ├── schema.prisma │ │ │ │ └── steps.json │ │ │ ├── 20191204173112-init │ │ │ │ ├── README.md │ │ │ │ ├── schema.prisma │ │ │ │ └── steps.json │ │ │ └── lift.lock │ │ ├── schema.prisma │ │ └── seed.ts │ ├── README.md │ ├── src │ │ ├── context.ts │ │ ├── generated │ │ │ └── schema.graphql │ │ ├── schema │ │ │ ├── Advertisement.ts │ │ │ ├── index.ts │ │ │ ├── JobLocation.ts │ │ │ ├── Mutation.ts │ │ │ └── Query.ts │ │ └── server.ts │ └── tsconfig.json └── yarn.lock
relevant dependencies from packages/server/package.json:
"dependencies": {
"@prisma/photon": "2.0.0-preview017.2",
"graphql": "14.5.8",
"graphql-yoga": "1.18.3",
"nexus": "0.12.0-rc.5",
"nexus-prisma": "0.6.1"
},
"devDependencies": {
"@prisma/sdk": "^0.0.76",
"@types/node": "12.12.14",
"@types/ws": "6.0.4",
"prisma2": "2.0.0-preview017.2",
"ts-node": "8.5.3",
"ts-node-dev": "1.0.0-pre.44",
"typescript": "3.7.2"
},
RafaelKr
on 4 Dec 2019
@RafaelKr Thank you for the information. My project is also a multi-workspace one, and I just tarted to wonder whether that may be the root cause…
kripod
on 4 Dec 2019
I just copied my packages/server files to a standalone folder and getting the same error. So probably it's not the cause.
RafaelKr
on 4 Dec 2019
I'm using an environment variable for my database url in the schema.prisma file.
datasource db {
provider = "postgresql"
url = env("POSTGRES_URL")
}
By starting the server with DEBUG=* yarn start I could easily track down what caused the error for me:
engine stderr error: Environment variable not found: POSTGRES_URL.
--> schema.prisma:7
|
6 | provider = "postgresql"
7 | url = env("POSTGRES_URL")
8 | }
|
+15ms
Error:
Invalid `photon.()` invocation in /path/to/project/node_modules/nexus-prisma/src/builder.ts:238:18
234 const photon = this.getPhoton(ctx)
235 assertPhotonInContext(photon)
236 return photon[mappedField.photonAccessor][
237 mappedField.operation
→ 238 ](args
undefined target="exit" timestamp="2019-12-04T19:34:15.893Z" fields={"message":"1"}
at PhotonFetcher.<anonymous> (/path/to/project/node_modules/@prisma/photon/index.js:54:27)
at Generator.throw (<anonymous>)
at rejected (/path/to/project/node_modules/@prisma/photon/index.js:6:65)
I just forgot to set the POSTGRES_URL environment variable for the dev script 🤦🏻♂️
I simply had to update my package.json script and now it's working perfectly! (I'm using the dotenv node plugin and have a .env file at the same level as my packages/server/package.json)
- "dev": "ts-node-dev --no-notify --respawn --transpileOnly src/server",
+ "dev": "ts-node-dev -r dotenv/config --no-notify --respawn --transpileOnly src/server",
But Prisma should definitely output at least a warning that this env var is not set.
RafaelKr
on 4 Dec 2019
But Prisma should definitely output at least a warning that this env var is not set.
💯
jasonkuhrt
on 4 Dec 2019
@RafaelKr Thank you for the thorough investigation! I’m currently using SQLite for its simplicity, but it may cause trouble on AWS Lambda because of the read-only file system…
kripod
on 4 Dec 2019
I just thought this further and came to the conclusion that Prisma always outputs that error when it can't reach the database. To check that, I shut down my Postgres Docker container and my assumption was confirmed.
So I would recommend the following things:
- The error
Invalid `photon.()` invocation in ...is not helpful. The root cause is an unsuccessful database connection/query, so this is the real error that should be logged. - Prisma should check if the database is available on startup and output a warning if not. For example by using
SELECT 1.
RafaelKr
on 4 Dec 2019
The error Invalid
photon.()invocation in ... is not helpful. The root cause is an unsuccessful database connection/query, so this is the real error that should be logged.
nexus-prisma lib (this repo) should be able to help with ☝️ . It might be the most actionable thing for this issue in this repo.
jasonkuhrt
on 4 Dec 2019
I have the same error with different cause, what I did is to run photon in a plain play.js then node play.js. Then I found the error is about I have different formats of datetime that have been saved from other source other than photon.
Otherwise, the error message from the response is unreadable and been truncated.
Albert-Gao
on 9 Dec 2019
Now that we have Nexus, this point is obsolete https://github.com/graphql-nexus/nexus-schema-plugin-prisma/issues/546#issuecomment-561847100. Also 6 months of work on Prisma Client has taken place. Going to close this issue. Please open new ones if new issues are encountered. ty!
jasonkuhrt
on 11 Jun 2020
Related issues
malekjaroslav
·
5Comments
RAW4RMCS
·
3Comments
macrozone
·
3Comments
jamesopti
·
4Comments
marticrespi
·
4Comments
Most helpful comment
I'm using an environment variable for my database url in the schema.prisma file.
By starting the server with
DEBUG=* yarn startI could easily track down what caused the error for me:I just forgot to set the
POSTGRES_URLenvironment variable for thedevscript 🤦🏻♂️I simply had to update my package.json script and now it's working perfectly! (I'm using the
dotenvnode plugin and have a.envfile at the same level as my packages/server/package.json)But Prisma should definitely output at least a warning that this env var is not set.