Prisma watercooler
March 20, 2019 at 8:32amPrisma watercooler
March 20, 2019 at 8:32amJuly 24, 2019 at 9:41pm
Hi, does anyone know why this error is?
July 31, 2019 at 5:09pm
This error appears Is the node version low?
August 4, 2019 at 6:59pm
August 29, 2019 at 6:20pm
Hello...Please help me out with this error. already tried changing docker-compose file but same error.
Docker-Compose
version: '3'services:prisma:image: prismagraphql/prisma:1.11restart: alwaysports:- "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-secretdatabases:default:connector: mongodbhost: 192.168.65.2port: '4406'database: truck.peschema: publicuser: adminpassword: moviesmigrations: false
Docker-Compose
version: '3'services:prisma:image: prismagraphql/prisma:1.11restart: alwaysports:- "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-secretdatabases:default:connector: mongodbhost: 192.168.65.2port: '4406'database: truck.peschema: publicuser: adminpassword: moviesmigrations: false
Please do note that changing host: to host.docker.internal also not working
September 3, 2019 at 7:49am
I added field Permission and got this error. Plz help me
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.
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!
September 19, 2019 at 7:03am
What the fuck is that plz
What the fuck is that plz
Prisma:1.34 container is infinity loop
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
December 28, 2019 at 5:04am
July 15, 2020 at 1:57am
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
did you solve this
July 15, 2020 at 8:08am
August 2, 2020 at 5:01pm
Hello Everyone I am new to Prisma & I am facing an issue & I am not sure how to resolve it
The details are:-
```model Story {
id Int (autoincrement())
storyNumber String
createdAt DateTime (now())
type String?
priority String?
title String?
state String
description String?
itemAuthor User (name: "CreatedPosts", fields: [itemAuthorId], references: [id])
itemAuthorId Int
itemAssigned User? (name: "AssignedPosts", fields: [itemAssignedId], references: [id])
itemAssignedId Int?
}
model User {
id Int (autoincrement())
name String
email String
password String
links Link[]
votes Vote[]
itemCreated Story[] ("CreatedPosts")
itemAssigned Story[] ("AssignedPosts")
}```
My Mutation Object is:-
postStory(storyNumber: String!, type: String!, priority: String, title: String, state: String!, description: String, storyAssignedTo: Int): Story
The code is:-
const postStory = async (parent, args, context, info) => {const authorId = getUserId(context);if (!authorId) {throw new Error("Missing Token");}let payLoad = {storyNumber: args.storyNumber,type: args.type,priority: args.priority,title: args.title,state: args.state,storyAuthor: {connect: {id: authorId}}}let assignedToUser = await context.prisma.user.findOne({where: {id: args.storyAssignedTo}});if (assignedToUser) {payLoad = {...payLoad,storyAssignedTo: {connect: {id: assignedToUser.id}}}}const newStory = context.prisma.story.create({data: {...payLoad}});return newStory}
Whenever I execute this I get an Error
{"data": {"postStory": null},"errors": [{"message": "\nInvalid `prisma.story.create()` invocation in\n/Users/aditya.padhi/Documents/jiraclonebackend/src/resolvers/Mutation.js:112:43\n\n\n The change you are trying to make would violate the required relation 'StoryAuthor' between the `Story` and `User` models.","locations": [{"line": 2,"column": 3}],"path": ["postStory"]}]}
can someone suggest what exactly I am missing.?
Thank-You In Advance
September 16, 2020 at 4:28pm
storyAuthor
should be replaced by itemAuthor
and storyAssignedTo
by itemAssigned
inside your payload