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

September 19, 2019 at 7:04am
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

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
  • reply
  • like

July 15, 2020 at 8:08am
did you solve this
Hi, If I remember correctly (it's been a few monthes), I solved it by manually altering the Migration table that prisma uses. I deleted the problematic row and then retried the deployment and it succeeded as expected.
Edited
  • reply
  • like

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
  • reply
  • like

September 16, 2020 at 4:28pm
storyAssignedTo and storyAuthor are not Story model properties
  • reply
  • like
storyAuthor should be replaced by itemAuthor and storyAssignedTo by itemAssigned inside your payload
  • reply
  • like