Navigating from https://v1.prisma.io/docs/1.34/ then clicking 1.13 from the dropdown takes you to github not prisma 1.13 docs

When I try to uninstall prisma 1 globally:

npm uninstall -g  prisma

it shows me this:

up to date in 0.03s

Like it's updating instead of uninstalling

Can anyone make sense of this? I fired up my ui and api using prisma 1 today for the first time in about a month and I get this cryptic message:

🚀 Server ready: /graphql
[GraphQL error]: Message: Project not found: 'four-players-co~four-players-co@dev%22%20', Location: undefined, Path: undefined
[Network error]: Error: Project not found: 'four-players-co~four-players-co@dev%22%20'
(node:95189) UnhandledPromiseRejectionWarning: Error: Project not found: 'four-players-co~four-players-co@dev%22%20'
    at BatchedGraphQLClient.<anonymous> (.../node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:69:35)
    at step (.../node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:40:23)
    at Object.next (.../node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:21:53)
    at fulfilled (.../node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:12:58)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:95189) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see <https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode>). (rejection id: 1)
(node:95189) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

What’s happening??

Prisma deploy does not deploy the datamodel. It shows that the deployment is successful. But the new datamodel does not appear in the prisma playground or in prisma admin.

Is anyone currently running a horizontal scaling prisma deploy with AWS Fargate? Everyone in github seems to have switched over to Kubernetes, but I'm not sure if I know how to pull that off. It looks like you can just have a non-management api enabled cluster running all your loads. And then you can have a completely independent server that has the management API enabled whenever you need to just run migrations. Am I correct in that assumption as mentioned in this comment: https://github.com/prisma/prisma1/issues/2850#issuecomment-480073610 I'm going to be attempting to get Prisma 1 horizontal scaling working with Fargate and RabbitMQ. We can't afford to switch to Prisma 2 for a little while, especially since it will probably take us a couple of months, and the nexus schema stuff still doesn't seem to be super settled... seeing as how it fluctuated about 3 major times over the past 2 years.

If I had a prisma 1 database, that has been modified to work with prisma 2, what's the right way to delete all data inside wile keeping the structure of tables and not messing with any prisma config?

When an updateFoo mutation is executed/resolved, is there some easy way to see the diff? Do I have to request the object from the db to compare?

Hello everyone! We're thrilled to announce that all three Prisma 2 components are production ready 🚀 ✅ Prisma Client ✅ Prisma Migrate ✅ Prisma Studio Check out the blog post and feel free to retweet 💚 If anyone is having trouble with the Prisma 1>2 migration, don't hesitate to ping me, we're actively working with several users to complete the migration successfully.

Hi, does anyone know if I do a query like this:

prisma.users({ where: { id_in: [1, 2, 3] } });

The order of the returned entities will be the same as the order of the array passed to the query?

Hello Everyone!! I am planning to migrate M:M to 1:1 relationship. Has anyone done this before using prisma 1.34 without any data loss and down time? The manual process is expensive.

On the server side, with the prisma client, I hook into the resolvers to trigger additional things, including potentially generating additional objects (add connect or create to the objects). Is there some similar way to hook into what is created via such create-objects? For my purposes, I can still do these things in the resolver, but it becomes more messy.

Does anybody know what the default connection limit was for Prisma Server when using it with Postgres?

Has anyone tried to disable the

playground

per these instructions: https://v1.prisma.io/forum/t/graphcool-playground-options-to-disable/2947/6 ? I'm getting an error trying to set it to `false`:

Type 'boolean' is not assignable to type 'string | false'.

Hi, currently prisma1 is maitained, but what is the end of life of this project? (currently thinking should i migrating prisma1 to prisma2 or not)

hi everyone, I'm using 

graphql

 and 

prisma

 with postgres database, when i try to deploy 

schema.graphql

 file with 

prisma1 deploy

 command it gives me an error.

{
  "data": {
    "addProject": null
  },
  "errors": [
    {
      "message": "Whoops. Looks like an internal server error. Search your server logs for request ID: local:ckoj44v3i02hc0877ny7w1j6q",
      "path": [
        "addProject"
      ],
      "locations": [
        {
          "line": 2,
          "column": 9
        }
      ],
      "requestId": "local:ckoj44v3i02hc0877ny7w1j6q"
    }
  ],
  "status": 200
}

docker logs:

Warning: Management API authentication is disabled. To protect your management server you should provide one (not both) of the environment variables 'CLUSTER_PUBLIC_KEY' (asymmetric, deprecated soon) or 'PRISMA_MANAGEMENT_API_JWT_SECRET' (symmetric JWT).

{"key":"error/unhandled","requestId":"local:ckoj44v3i02hc0877ny7w1j6q","payload":{"exception":"org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint \"Project_pkey\"\n Detail: Key (id)=(reviews$default) already exists.","query":" mutation addProject($name: String! $stage: String! $secrets: [String!]) {\n addProject(input: {\n name: $name,\n stage: $stage\n secrets: $secrets\n }) {\n project {\n name\n }\n }\n }\n ","variables":"{\"name\":\"reviews\",\"stage\":\"default\",\"secrets\":null}","code":"0","stack_trace":"org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2433)\\n org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2178)\\n org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:306)\\n org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441)\\n org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365)\\n org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:155)\\n org.postgresql.jdbc.PgPreparedStatement.execute(PgPreparedStatement.java:144)\\n com.prisma.connector.shared.jdbc.SharedSlickExtensions.$anonfun$insertToDBIO$1(SharedSlickExtensions.scala:37)\\n com.prisma.connector.shared.jdbc.SharedSlickExtensions.$anonfun$insertToDBIO$1$adapted(SharedSlickExtensions.scala:37)\\n com.prisma.connector.shared.jdbc.SharedSlickExtensions.$anonfun$jooqToDBIO$1(SharedSlickExtensions.scala:56)\\n slick.jdbc.SimpleJdbcAction.run(StreamingInvokerAction.scala:70)\\n slick.jdbc.SimpleJdbcAction.run(StreamingInvokerAction.scala:69)\\n slick.basic.BasicBackend$DatabaseDef$$anon$3.liftedTree1$1(BasicBackend.scala:276)\\n slick.basic.BasicBackend$DatabaseDef$$anon$3.run(BasicBackend.scala:276)\\n java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\\n java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\\n java.lang.Thread.run(Thread.java:748)","message":"ERROR: duplicate key value violates unique constraint \"Project_pkey\"\n Detail: Key (id)=(reviews$default) already exists."}}

Good morning. I’m running into a new issue - when I try to deploy changes to my Prisma instance setup on Heroku, it fails with a heroku 503 error:

$ npm run deploy

> offroad-club-backend@1.0.0 deploy /offroad-api
> prisma deploy --env-file variables.env

Deploying service `default` to stage `default` to server `fp-prod` !

ERROR: GraphQL Error (Code: 503)

{
  "error": "<!DOCTYPE html>\n\t<html>\n\t  <head>\n\t\t<meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n\t\t<meta charset=\"utf-8\">\n\t\t<title>Application Error</title>\n\t\t<style media=\"screen\">\n\t\t  html,body,iframe {\n\t\t\tmargin: 0;\n\t\t\tpadding: 0;\n\t\t  }\n\t\t  html,body {\n\t\t\theight: 100%;\n\t\t\toverflow: hidden;\n\t\t  }\n\t\t  iframe {\n\t\t\twidth: 100%;\n\t\t\theight: 100%;\n\t\t\tborder: 0;\n\t\t  }\n\t\t</style>\n\t  </head>\n\t  <body>\n\t\t<iframe src=\"//www.herokucdn.com/error-pages/application-error.html\"></iframe>\n\t  </body>\n\t</html>",
  "status": 503
}

Get in touch if you need help: <https://slack.prisma.io>
To get more detailed output, run $ export DEBUG="*"
(node:55959) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! offroad-club-backend@1.0.0 deploy: `prisma deploy --env-file variables.env`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the offroad-club-backend@1.0.0 deploy script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /.npm/_logs/2021-05-13T06_17_17_151Z-debug.log

What was the connection limit and pool timeout in Prisma 1? (would like to use them with Prisma 2)

I'm still not able to get the Kubernetes setup working fully on AWS EKS, been working on it for a month, I got the ALB up and running, but the generated Target Group fails health checks when I'm pointing to 

/status

, and I am not sure if the prisma pods are even capable of talking to my database. When I 

exec

 into the pods and run a 

netstat -an

 they show me that it's listening on port 

3306

. But I get a 502 bad gateway response when I hit the load balancer end point. Is there anyone who would be willing to help me troubleshoot, I'll gladly pay you for your time, just DM me.

Anyone ever run into this issue after running prisma deploy?

It worked for my staging endpoint but now not working for prod. I added a couple of new required fields to a data model

Did anyone use their nexus generated prisma client in a google cloud function? How did you structure your function projects? This generated code will be needed in multiple functions as I envision my architecture

I already use the prisma client in a different, more traditional, server project that runs in cloud run instead.

Well, the nexus generated part isn't necessary, only need prisma client actually

Found some examples using prisma2, so maybe I'll figure this out yet

With the MongoDB connector, can I do stuff like use the $inc-directive via the Prisma-API?

Hi there

I have a question about Prisma1

In my MongoDB database profiler, I am seeing a multitude of OR operations, but I can't seem to locate the query itself. I know which collection the slow queries are running on, but I cannot seem to find any OR operations within my Apollo Queries... Any reason why Prisma would be running OR operations under the hood?

What's the best way to ensure that Subscriptions are reliable?

Someone facing docker problem on mac m1? Just prisma 1.34 is have some problem no idea?!