https://www.prisma.io/ logo
Join Slack
Powered by
# prisma-whats-new
  • m

    Muenze

    03/08/2018, 4:33 PM
    Hi guys. I am looking for GraphCool + Ionic tutorial if any. I am having some issues in sending data to GraphCool's database, not everything is being recorded.
    m
    • 2
    • 1
  • d

    David Yin

    03/08/2018, 4:45 PM
    Hey guys i was looking at the documentation for nested connect mutations: https://www.graph.cool/docs/reference/graphql-api/mutation-api-ol0yuoz6go/#nested-connect-mutations it seems to suggest that if you were to supply a new list of connections that it would replace the current to many relations with the new one but it doesn't seem to be the cause for me rather when i supply a list of ids to connect it appears to append those results any idea why that would be?
  • d

    David Yin

    03/08/2018, 4:46 PM
    heres the example before i have:
    Copy code
    {
      "data": {
        "updateCohort": {
          "id": "cjehv04a5005z0111sytdz4gx",
          "users": [
            {
              "id": "cje63e3a8000p0111ead5pi54"
            },
            {
              "id": "cje63gfpi00110111sotp3o77"
            }
          ]
        }
      }
    }
  • d

    David Yin

    03/08/2018, 4:47 PM
    then after running
    Copy code
    mutation {
      updateCohort(data:{users:{connect:[ {id: "cje63e3a8000p0111ead5pi54"}]}}, where:{id:"cjehv04a5005z0111sytdz4gx"}){
        id
        users {
          id
        }
      }
    }
  • d

    David Yin

    03/08/2018, 4:47 PM
    i still have the above result returned
  • d

    David Yin

    03/08/2018, 4:47 PM
    i would expect that only the supplied id be the only element in user as suggested from the docs
  • r

    ratkinson

    03/08/2018, 8:07 PM
    Is anyone else having trouble logging in to the graphcool console? https://console.graph.cool/login
    s
    • 2
    • 2
  • r

    ratkinson

    03/08/2018, 8:07 PM
    I keep getting "internal server error"
  • r

    ratkinson

    03/08/2018, 8:07 PM
    my request id:
    eu-west-1:system:cjeixyjgs0qu70162csr95hyt
  • t

    tz

    03/09/2018, 3:51 AM
    I run into a prisma deployment issue. I can run “prisma deploy” without any problem on my local machine. The service is deployed to prisma cloud. Then I tried to copy the same code to the staging server and run “prisma deploy” again, it failed. And then I tried “prisma login”, and it failed with basically the same error message. Here is the error that I got:
  • t

    tz

    03/09/2018, 3:53 AM
    Authenticating... client Sending query to cloud api +0ms client https://api.cloud.prisma.sh +0ms client mutation { client requestCloudToken { client secret client } client } +0ms client undefined +0ms client { headers: {} } +0ms Opening https://app.prismagraphql.com/cli-auth?secret=$2a$08$QmtZK0uK/85ZC9MDNIxqdu in the browser client Sending query to cloud api +456ms client https://api.cloud.prisma.sh +0ms client query ($secret: String!) { client cloudTokenRequest(secret: $secret) { client secret client token client } client } +0ms client { secret: ‘$2a$08$QmtZK0uK/85ZC9MDNIxqdu’ } +0ms client { headers: {} } +0ms Error: Exited with code 3 at ChildProcess.cp.once.code (/usr/local/share/.config/yarn/global/node_modules/opn/index.js8413) at Object.onceWrapper (events.js31730) at emitTwo (events.js12613) at ChildProcess.emit (events.js2147) at maybeClose (internal/child_process.js92516) at Socket.stream.socket.on (internal/child_process.js34611) at emitOne (events.js11613) at Socket.emit (events.js2117) at Pipe._handle.close [as _onclose] (net.js55412)
  • l

    Luke

    03/09/2018, 3:57 AM
    Hey
  • l

    Luke

    03/09/2018, 3:58 AM
    so I can’t see my service in https://app.prisma.sh
  • l

    Luke

    03/09/2018, 3:58 AM
    but I see
  • l

    Luke

    03/09/2018, 3:58 AM
    Copy code
    ➜  lyra-api prisma info
    Service Name: lyra-api
    
      dev (cluster: `prisma-us1`)
    
        HTTP:       <https://us1.prisma.sh/public-pieeagle-566/lyra-api/dev>
        Websocket:  <wss://us1.prisma.sh/public-pieeagle-566/lyra-api/dev>
  • l

    Luke

    03/09/2018, 3:59 AM
    am I missing something?
  • l

    Luke

    03/09/2018, 3:59 AM
    I logged in with
    prisma-cli
    before deploying
  • l

    Luke

    03/09/2018, 4:01 AM
    @here anyone?
  • t

    tz

    03/09/2018, 4:02 AM
    did you do ‘prisma deploy’?
  • l

    Luke

    03/09/2018, 4:02 AM
    yeah
  • l

    Luke

    03/09/2018, 4:03 AM
    Copy code
    ➜  lyra-api prisma deploy
    Deploying service `lyra-api` to stage `dev` on cluster `public-pieeagle-566/prisma-us1` 298ms
    Service is already up to date.
    
    Hooks:
    Checking, if schema file changed 588ms
  • l

    Luke

    03/09/2018, 4:04 AM
    https://cl.ly/2k1X2C2m2F0r
    l
    • 2
    • 1
  • t

    tz

    03/09/2018, 4:04 AM
    I can connect with your endpoint though
  • t

    tz

    03/09/2018, 4:05 AM
    wait, it says server cannot be reached.
  • l

    Luke

    03/09/2018, 4:06 AM
    I basically did prisma init
  • l

    Luke

    03/09/2018, 4:06 AM
    then logged in
  • t

    tz

    03/09/2018, 4:08 AM
    this is strange. I can deploy on my local machine without any problem. I do remember there was a step when a browser window pops up and you have to click on grant permissions.
  • l

    Luke

    03/09/2018, 4:08 AM
    re did it
  • l

    Luke

    03/09/2018, 4:08 AM
    and it worked with a fresh project
  • l

    Luke

    03/09/2018, 4:08 AM
    stranger
1...603604605...637Latest