menu

Prisma

🔴 The Prisma Spectrum community is not officially managed by Prisma's support team any more. Please seek help on GitHub or on Slack instead. Learn more: https://spectrum.chat/prisma/general/where-and-how-to-best-seek-help-with-questions-problems~687a1b8f-8658-4df3-8849-ea5ab3503f28

Channels
Chat
view-forward
# All channels
view-forward
# General
view-forward
# Beta
view-forward
# Community
view-forward
# GraphQL
view-forward
# OSS
view-forward
# Random
view-forward
Team

Prisma watercooler

March 20, 2019 at 8:32am
Show previous messages

July 24, 2019 at 8:35pm
Prisma CLI version: prisma/1.34.0 (darwin-x64) node-v10.4.1
Prisma server version: 1.34.3
  • reply
  • like
Hi, does anyone know why this error is?
  • reply
  • like

July 31, 2019 at 5:09pm
  • reply
  • like
This error appears Is the node version low?
  • reply
  • like

August 4, 2019 at 6:59pm
wewe
  • reply
  • like
eq
  • reply
  • like

August 29, 2019 at 6:20pm
Hello...Please help me out with this error. already tried changing docker-compose file but same error.
  • reply
  • like
Docker-Compose
version: '3'
services:
prisma:
image: prismagraphql/prisma:1.11
restart: always
ports:
- "4466:4466"
environment:
PRISMA_CONFIG: |
port: 4466
# uncomment the next line and provide the env var PRISMA_MANAGEMENT_API_SECRET=my-secret to activate cluster security
# managementApiSecret: my-secret
databases:
default:
connector: mongodb
host: 192.168.65.2
port: '4406'
database: truck.pe
schema: public
user: admin
password: movies
migrations: false
  • reply
  • like
Docker-Compose
version: '3'
services:
prisma:
image: prismagraphql/prisma:1.11
restart: always
ports:
- "4466:4466"
environment:
PRISMA_CONFIG: |
port: 4466
# uncomment the next line and provide the env var PRISMA_MANAGEMENT_API_SECRET=my-secret to activate cluster security
# managementApiSecret: my-secret
databases:
default:
connector: mongodb
host: 192.168.65.2
port: '4406'
database: truck.pe
schema: public
user: admin
password: movies
migrations: false
Please do note that changing host: to host.docker.internal also not working
  • reply
  • like

September 3, 2019 at 7:49am
I added field Permission and got this error. Plz help me
  • reply
  • like

September 12, 2019 at 11:23am
I added field Permission and got this error. Plz help me
Just started getting the same issue using a similar set up to the stack used in Wesbos' sick fits. Was working fine about an hour ago and now this. Should be noted that I also can't view my service in the Prisma Console online.
  • reply
  • like
Just started getting the same issue using a similar set up to the stack used in Wesbos' sick fits. Was working fine about an hour ago and now this. Should be noted that I also can't view my service in the Prisma Console online.
I've just been on the Intercom chat with one of the reps at Prisma and my services are running fine again! Might be worth doing the same if your are still having that issue!
  • reply
  • like

September 19, 2019 at 7:03am
What the fuck is that plz
  • reply
  • like
What the fuck is that plz
Prisma:1.34 container is infinity loop
  • reply
  • like

November 21, 2019 at 9:21am
Hi there,
I have been trying to deploy a new datamodel on an existing Prisma service, but I get the following error:
ERROR: You can not deploy to a service stage while there is a deployment in progress or a pending deployment scheduled already. Please try again after the deployment finished.
{
"data": {
"deploy": null
},
"errors": [
{
"locations": [
{
"line": 2,
"column": 9
}
],
"path": [
"deploy"
],
"code": 4008,
"message": "You can not deploy to a service stage while there is a deployment in progress or a pending deployment scheduled already. Please try again after the deployment finished.",
"requestId": "local:ck38ht1h80hgf0836ndvrbrvj"
}
],
"status": 200
}
The problem is, it's been in that state for almost 36 hours now and I don't know how to kill that in progress deployment... I have tried restarting the Prisma service container but unfortunately the problem persists after reboot.
Any help would be very much appreciated !
Quentin
  • reply
  • like

December 28, 2019 at 5:04am
Hey all! Anyone here that can help me with a few questions? One involves and error I'm encountering while building tests and another about some datamodel erros that are getting tossed back at me
  • reply
  • like