Where to get error Stacktrace?

Issues GraphQL
, ,
#1

While using the graphic query interface I got this msg:

  "errors": [
    {
      "message": "Internal Server Error - a panic was trapped.  This indicates a bug in the GraphQL server.  A stack trace was logged.  Please let us know by filing an issue with the stack trace."
    }
  ]
}

where can I check this stacktrace?

#2

It should be there as a panic in the dgraph alpha logs`. So check the logs and share with his so that we can look into it.

#3

I’m not sure if it is possible on the SlashQL deployment. I’m trying to find it on the slash dashboard and also with the slash CLI but didnt get it yet.

The references I’ve found on the docs for logging seem to work only for deployed dgraph versions but not for the hosted version (slash).

Maybe I missed something. If you can share some document about it would be great.

Thanks!

#4

Hey @brmaeji,

This feature isn’t supported in slash yet. I’m not able to see any deployments created by you.
Can you please try to create another deployment, and notify me about it? I’ll be able to provide you the logs for that one.

1 Like
#6

Hey @brmaeji

Apologies for taking a few days to get back to you. We were able to get the logs and this is indeed a bug. We are trying to reproduce this on our end. Would it be possible for you to share the mutation which caused this and if possible the type definition of the nodes that you were trying to modify?

Once we are able to reproduce this, we should have a fix in a day or two.

#8

hey @brmaeji

Would it be possible for you to share the mutation which caused this and if possible the type definition of the nodes that you were trying to modify?

#9

hey @pawan, I’m trying to find it but I think it got lost in some notes file I overwrote with my last tests… sorry about that. I’ll try to reproduce it - I’m almost sure it was a GraphQL query that used both set and remove on the same property and that was the problem.