-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors are unhelpful #61
Comments
Thanks for the report, @felixfbecker I do wonder whether this is an issue with the error message itself (so dgraph-io/dgraph) or the way it ends up being displayed (this repo). @paulftw, could you check whether we could improve the error message on this repository by at least showing which of all of the mutations was actually wrong? |
Actually I noticed that the name of the predicate here was "contents", it was just not clear because it wasn't quoted and made sense as a sentence. But I think overall that would not help a lot - I'd still need a proper stack trace, maybe the index of the nquad in the list, the actual UID values of subject and object - anything that helps to find the bug |
Yeah, I think the message can be improved, yeah. |
I am running a mutation that fails with this error:
The mutation contains thousands of nquads, so I have no idea which one is wrong. I would expect the error to include some properties about which nquad failed to get added, at least the name of the predicate. The error code also always seems to be 2, and the stack trace doesn't include the user code.
As a comparison, errors from the node Postgres client
pg
have properties that specify the query, position, even the name of a column contraint that failed.The text was updated successfully, but these errors were encountered: