Closed andreasnoack closed 7 years ago
It seems the segfault generated is due to a WeakRefString being captured in a CapturedException
and then serializing, causing the pointer to be zero-ed.
The actual error is
Could not determine which type to promote column to.
Error reading file ./20160102043000.gkg.csv
Parse error at line 1306 at char 12476:
...U/VRVlo2XZZII/AAAAAAAAAW4/7lirGJoV3XA/s1600/3.PNG;...
____________________________________________________^
CSV column 20 is expected to be: TextParse.Field{String,TextParse.Quoted{String,TextParse.StringToken{String}}}("<string>", true, true, false, false, Nullable{Char}('\t'))
Sure enough, that line got truncated at 20 fields... The error is misleading. Fix upcoming.
The issue is fixed in that the error messages are correct now. I wonder if this is a problem with the data export itself... Should TextParse treat the remaining 7 fields as null? Or is an error saying "Expected more fields at the end of line" justified?
I was able to fix the issue by joining line 1307 and 1308. It seems there's a newline half way through a string field. Could it be possible that this was accidentally introduced?
Great. Just looked at the raw strings and the newline is definitely wrong.
on