(Had Prisma CLI v. 1.17, updated to 1.27 and same result)

It’s not possible to have an issue with whitespace in the secret, is it? It’s trimmed at the ends that’s for sure but I have a long secret which includes spaces

hmm spaces could be the issue

where was the secret generated? is it something that Prisma generates or that you do? I don’t really know about prisma JWT stuff but I know about JWT in general

It’s all in Prisma config and I’ve only used Prisma CLI to generate tokens so far

(Which is only an issue due to the short expiration time)

I’m tempted to test a new secret without spaces… but really? We’re just dealing with encoding strings here, and

prisma.yml

has it in quotes

spaces might be an issue with base 64 encoding

not sure if the secret is supposed to be base64 encoded in this case, but sometimes it is

Ok… well I’ll try changing the secret on a local instance

(I could be wrong about the spaces)

but might be worth a shot 🙂

I’m out of ideas 😄

Alright, my new best friend @ryan - looks like you were right about the spaces 😛

awesome! glad to hear it worked 👍

Thanks 🤘

Hey all, I have a db type w/ ~12,000 items that I want to run a tagging script through, some of the tags will hit 60%+ of the items which will then want to mutate each of them, so ~7000. Is a batched mutation best for this?

I have been concerned in the past with db load and tried to add pauses in between batches. Is this is a real concern or is there a better way to mitigate? Thanks for any help.

Hello world, I see in some projects based on prisma something that I can't explain myself, for example a type that could be like this:

type Model{
  id: ID!
  weight(unit: unit): Float #KG, LB
  text(locale: locale): String # EN, US, etc
}

How can I have a type like that in Prisma endpoint directly? Is it possible?

Has anyone experience with using DateTime as a type for a field? e.g.

startDate

and

endDate

?

I'm getting internal server errors and as it's on the demo server, I can't access the logs 😞

Huh, works fine when deployed to my own Heroku server

Worked itself out I guess 😅

Hello world 🙂 How did you solved server error issue like below?

Whoops. Looks like an internal server error. Search your server logs for request ID: ...

I don’t think I’m building my query the right way. I’ve got Prisma connecting to Postgres and I can do a successful query on localhost:4466. But I have this running in ApolloServer 2 and when I run that on localhost:4000 and do this query:

query { 
	users {
    id
    first_name
    last_name
    username
  }
}

I get this failure:

"message": "Field \"users\" argument \"first_name\" of type \"String!\" is required but not provided.",

There is a valid data row in the database.

hello, I have prisma version 1.12.0 running. Now i want to update to the latest version 1.27. What are the steps to upgrade? Do I also need to upgrade my docker container?

Hey friends! I've been encountering an error with my prisma-client inside of my nodejs app:

Error: Project not found: 'default_default'

I'm a little confused about how to address it. Facts: - generated prisma client successfully (using MongoDB) - running nodejs app, mongo, and prisma inside docker-compose - prisma server is running and client is connected (mongo logs -

Successfully authenticated as principal prisma on admin

) - was able to successfully add users via the prisma client into mongoDB at some point, can't figure out what I changed to break this Would really appreciate some experienced insight. Thanks!

@Steve Mason can you share your docker-compose? I am in the step of connecting an Atlas database to a prisma server in DO and until now I cant figure out how to do that

Would anyone here be interested in doing a Hangout on Nexus. Be good to chat and get the video on YouTube for others. Let me know if anyone is interested.

Hello people, does anyone know of a public repo of a production-ready prisma/apollo-server/prisma-nexus server?