Json parse error

Issues Dgraph Clients
,
1

Moved from GitHub dgraph-js/17

Posted by jeffkhull:

Version: 1.0.2 (also applies to 1.0.3)
Dgraph version: 1.0.2

After running a query of the form via txn.query(…):

{
    classes(func: eq(<${sp.VertexType}>, "Class"), orderasc: ${sp.Name}) {
      uid: _uid_
      name: ${sp.Name}
      ...
}

Within your method Response.getJson(), the call to super.getJson() returns a string that is not valid Json:

"classes": [{"name":....

This results in a JSON parse error, “Unexpected token : in JSON at position 9”

Was there a recent change that would have changed the format of the string returned from super.getJson() so that it is missing an opening brace?

EDIT: the value returned from super.getJson() is determined to be Uint8 and gets put through the u8ToStr function.

EDIT 2: I have found that the last character returned from super.getJson() is ASCII character #26 (“SUBSTITUTE”). When I append a brace to the front of the result, and remove this “SUBSTITUTE” from the end, the string is valid JSON. So it looks like the query result may be incorrectly offset by 1 character.

2

gpahal commented :

Can you post the full query and response if it’s not confidential? I am not able to reproduce this.

3

jeffkhull commented :

Not a problem, I will do this first thing next week. I’m just now learning how the auto-generated protobuf code works and was planning to dig in a bit more there. If I’m not mistaken, the grpc module runs native code. I’m running the client on windows and accessing dgraph running on Ubuntu inside of VirtualBox. I’m not sure if the windows platform may have something to do with this.

Either way, I will post an exact query / response next week, and will try to dig further into the generated code to see if I can find out what is going on.

4

jeffkhull commented :

Somehow I’m not able to repro this morning. Will reopen when / if it comes up again.

5

roscioli commented :

I’m getting the same problem with 1.0.3

6

roscioli commented :

Seems like the first { is missing and is breaking the JSON.parse in /lib/types.js line 80.

7

jeffkhull commented :

@roscioli , I’m getting it again too, but I haven’t bothered to re-open the issue until I can produce a solid repro. I’ll re-open now though since you’re also getting the issue.

Have you noticed a pattern with the volume of data you’re returning in the queries that fail? The only pattern I’ve noticed so far is that the failures happen when the response payloads are large.

8

jeffkhull commented :

I’ve put this patch code in the library. I’m going to add some code to write the failed request / responses to the filesystem for repro purposes, but I haven’t done it yet.

if(!jsonStr.startsWith('{')) {
	console.error('FYI - in patched code.  charcode at beginning: ' + jsonStr.charCodeAt(0) + ' and end: ' + jsonStr.charCodeAt(jsonStr.length - 1))
	jsonStr = ('{' + jsonStr)
	jsonStr = jsonStr.substr(0, jsonStr.length - 1)
}
9

roscioli commented :

@tamethecomplex yes, on big data sets this is happening to me.

10

roscioli commented :

That patch does work. Would be great to get a real fix in though.

11

roscioli commented :

What is super curious though is that when I take the raw JSON string (which was throwing the error) and prepend { and run it through a JSON linter, the linter says it is fine JSON. However, when I updated the code with jsonStr = ('{' + jsonStr), the code was still getting a JSON parse error but this time it said there was an extra } at the end… Are there phantom characters or something or am I just going crazy?

12

jeffkhull commented :

@roscioli yes definitely - what I found is that when the leading ‘{’ is missing, the trailing character is ASCII character ID 26, “substitute”. That character also broke the parse - so whenever I append the ‘{’, I also have to remove the last character.

13

gpahal commented :

Has anyone been able to reproduce this? It seems the problem might be with the grpc server which will also affect other Dgraph clients. It’s better to find and resolve the root cause.

14

jeffkhull commented :

@gpahal , I just added some more logging that will allow me to provide a specific query / response for a repro. Will let you know when I have some good data. Probably by the end of the week.

15

jeffkhull commented :

@gpahal , I was able to reproduce this issue. All I had to do was try to get a query result that has a sufficiently large response. The repro is available here: js_issue_repro/dgraph-js/issue_17 at master · cyphercider/js_issue_repro · GitHub.

The error you’re looking for us “Unexpected token :” being thrown from the response.getJson() method:

image
image802×188 18.7 KB

16

emhagman commented :

I am also having this issue on an array returning 9000+ items.

17

gpahal commented :

This issue is either caused by Dgraph server returning incorrect JSON string in grpc response or the grpc node library. I’ll try to reproduce this issue and also use the Go client and raw HTTP to figure out what is happening.

18

gpahal commented :

There was a bug in a utility function. This error should not show in v1.1.1-beta.1. If you face problems with that version, please let me know.

19

jeffkhull commented :

@gpahal , I will let you know, thank you!

20

jeffkhull commented :

@gpahal , would it be possible for you to publish the beta to npm? Or I can clone and link if that is better for you. I didn’t see either a branch or a tag for the beta.