You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The input CSV is not well formed, however I expect fread would pin-point the wrong pieces.
From the comma_sequence_per_line.csv it looks like I have non-teriminated quoted field at line 9.
Ultimately I would like fread to report exactly that: "possible missing quote for the field started at line 9".
Here's the proper (at least it does not crash R) error message (I've shortened all the words and it made fread to work):
> fread("fread_line_error.csv")
Errorin fread("fread_line_error.csv") :Field25online9startswith quote (") but then has a problem. It can containbalanced unescaped quoted subregions but if it does it can't contain embedded\n as well. Check for unbalanced unescaped quotes: "D#7 - OK K-V N Y#3...
It looks like
fread
does not like long lines when printing error messages.When the line gets long,
fread
just crashes.The sample data can be found in this gist: https://gist.github.com/vlsi/3b9e9e986bf952360397
The input CSV is not well formed, however I expect
fread
would pin-point the wrong pieces.From the
comma_sequence_per_line.csv
it looks like I have non-teriminated quoted field at line 9.Ultimately I would like
fread
to report exactly that: "possible missing quote for the field started at line 9".Here's the proper (at least it does not crash R) error message (I've shortened all the words and it made
fread
to work):Here's abort case:
Here's
lldb
backtrace. I am sorry I have no idea how to enable debug support to make local variables visible tolldb
.The text was updated successfully, but these errors were encountered: