Affie commented 5 years ago

The .data Array{Uint8,1} returned has a bunch of 0x00 at the end causing the JSON string in it to be miss-formed. It seems to work with similar code on a small piece of data.

GearsAD commented 5 years ago

WIP, more to follow on Wednesday

GearsAD commented 5 years ago

Okay, this we have this figured out. Its actually two bugs:

Our gateway was doing strange encoding on the binary data. Thats why we could only see it on the running cloud server. That explains why it was larger. Ive changed the SDK to work with strings and it base64 encodes binary data when you use the helper encodeBinaryData.
In addition, our server-side stream reader was truncating the data if it was large. Subequently changed out and im redeploying it tonight. That explains why we saw the ends of the files as zeros and only saw it with data > a couple kb

So, two changes made. @affie you may need to switch back to strings for data. But otherwise should be ok.

GearsAD commented 5 years ago

108

GearsAD commented 5 years ago

Can we confirm that all is ok?

GearsAD / GraffSDK.jl

Possibly wrong big data serialization #106

108