https://www.prisma.io/ logo
Join SlackCommunities
Powered by
# orm-help
  • a
    Or react-apollo?
    s
    • 2
    • 1
  • b
    @Andy Fang I'm using Apollo with ReasonML.
  • j
    Hi folks! using 
    graphql-request
    and trying to figure out how best to mock the API responses using jest. Any recommendations/advice?
  • s
    Anyone have experience with updating your prisma server on heroku to the newest version?
  • a
    Is graphcool down?
    h
    t
    p
    • 4
    • 3
  • p
    Hey prisma team, there seems to be 503 errors across a number of projects for the graphcool Simple API
    👀 1
    🙋‍♂️ 2
  • h
    Hi all, We are currently experiencing some issues with DockerHub which is affecting our GraphCool deploy. We are working on bringing GraphCool back up as quickly as possible 🙏
    🙏 10
    💯 2
  • b
    yep, graphcool cloud are not working! 😖
    😩 4
  • j
  • j
    You can follow that page for status
  • j
    For the people that need something concrete to show management 😉
  • n
    Graphcool status page says that everything is fine 😖 https://status.graph.cool/ Docker hub is facing authentication issues with degraded performance to log in, log out and reset password. Why the already deployed Graphcool servers shutted down? Graphcool docker hub account was involved with last week exploit?
    😖 1
  • n
    Graphcool is now working for me
  • n
    Very unstable
  • b
    Exist some way to get access to the Mysql database cloud service of a Graphcool service? Because the export/import not work properly
  • b
    Or how we can obtain a backup of the current database in the cloud service?
  • t
    Seems to be up for me too
  • m
    Our account was not compromised in the incident. What caused the downtime today is that we were not able to pull images from docker hub due to some rate limiting that they put in place on their side. In the last hours we started to work around the rate limiting.
    😥 1
    👍 6
  • n
    Simple graphql api is working for me CLI connection still down Graphcool admin is unstable
    🙋‍♂️ 1
  • n
    Hi all, I'm not sure what happened but I'm getting a really weird error when trying to run 
    prisma generate
    (details in thread)
    • 1
    • 8
  • k
    Hey guys, I'm trying to check existence of some records base on multiple fields since there's no feature like unique together in prisma yet i came with the idea of checking existence of them before creating, But in my case i have an array of objects and i have to map through them... finally i wrote it out like this:
    Copy code
    musics.map(async (music) => {
            let isMusicExists = await context.prisma.$exists.musicDirectory({
                AND: [
                    {
                        directoryId,
                        musics_some: {
                            trackId: music.trackId,
                            trackService: music.trackService
                        }
                    }
                ]
            });
            if (isMusicExists){
                throw new Error('This music is already added in this place!')
            }
        });
    this piece of code is in middle of my revolver, What i expect after receiving duplicate record is throwing an error and stop the execution furthermore but what i get in console is:
    Copy code
    (node:11309) UnhandledPromiseRejectionWarning: Error: This music is already added in this place!
    at musics.map (/home/kianoosh/MyApp/resolvers/Mutation.js:384:23)
    at processTicksAndRejections (internal/process/task_queues.js:86:5)
(node:11309) 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(). (rejection id: 2)
    I tried to use catch but it didn't make any difference after all the error is just printing in console and doesn't stop anything.
    c
    j
    • 3
    • 6
  • j
    I've been following a tutorial series (Wes Bos's Advanced-React course) and when I most recently tried to deploy some changes, I've been getting the error "One field of the type 
    User
    must be marked as the id field with the 
    @id
    directive." but I have version 1.17.1 of prisma installed and before we just had to have "id: ID! @unique" and I'm not sure what changed.
    s
    d
    • 3
    • 8
  • d
    Hi, everyone. Is there any documentation about 
    @scalarList
    ? I updated my Prisma version so I could try Prisma Admin and now, when deploying, I’m getting the `Valid values for the strategy argument of 
    @scalarList
    are: RELATION.` errors. Thanks.
    j
    • 2
    • 3
  • p
    Hello on prisma.sh sometimes the websocket working and sometimes now, why
  • m
    Hi Guys, do I understand correct that prisma is not supporting mssql connections at the moment? best regards
    n
    • 2
    • 1
  • r
    I’ve deployed a Prisma Cloud server (https://www.prisma.io/cloud) via Heroku. Locally I’m using the 1.31 release but the server is still on 1.23 - I therefore get a warning about mismatched versions when I deploy. Is there a way to update the version of the Prisma Cloud server to the latest - if not, is there any release plan as to when the new version will be available on Prisma Cloud?
    n
    • 2
    • 2
  • d
    I installed the latest version of Prisma (1.31.2) and set that version in 
    docker-compose.yml
    but I’m getting an error when trying to set up the database.
    Copy code
    ➜ git:(master) ✗ prisma --version
Prisma CLI version: prisma/1.31.2 (darwin-x64) node-v10.15.3
➜ git:(master) ✗ docker-compose up -d
Pulling prisma (prismagraphql/prisma:1.31.2)...
ERROR: manifest for prismagraphql/prisma:1.31.2 not found
    Looking on Docker, I don’t see a tag for that version.
    h
    n
    • 3
    • 3
  • d
  • k
    I’m getting this error although the definition of the input type is:
    Copy code
    export type PaddleSubscriptionWhereUniqueInput = AtLeastOne<{
  id: ID_Input;
  subscriptionId?: String;
}>;
    h
    • 2
    • 1
  • g
    Could anybody here help me with 
    graphql-code-generator
    and 
    prisma
    type mismatch on returning promise. That is, for this field resolver:
    Copy code
    customer: async (root, args, context) => {
    try {
      await ifCustomerOwnsThisResource(context, {
        cartItems_some: {
          id: root.id
        }
      });
      return await context.prisma.customerCartItem({ id: root.id }).customer();
    } catch (error) {
      console.error(error);
    }
  },
    I am getting this error:
    Copy code
    src/resolvers/cartResolvers.ts:25:3 - error TS2322: Type '(root: CustomerCartItem, args: {}, context: IContext) => Promise<Customer>' is not assignable to type 'Resolver<Customer, CustomerCartItem, IContext, {}>'.
  Type '(root: CustomerCartItem, args: {}, context: IContext) => Promise<Customer>' is not assignable to type 'ResolverFn<Customer, CustomerCartItem, IContext, {}>'.
    Type 'Promise<Customer>' is not assignable to type 'Customer | Promise<Customer>'.
      Type 'Promise<import("G:/graphql/prod/graphql-server/src/generated/prisma-client-ts/index").Customer>' is not assignable to type 'Promise<import("G:/graphql/prod/graphql-server/src/generated/resolvers-types").Customer>'.
    From what I get, 
    prisma
    returns 
    interface CustomerPromise
    for chained query, while 
    Promise<Customer>
    is expected as return expression by 
    graphql-code-generator
    . How to fix that?
    d
    h
    • 3
    • 5
1...263264265...637Latest