Closed iriberri closed 9 years ago
It'd be great if you can provide a test suite. Could you sort the ones you found for a couple of weeks from now on? It should not cost you much and it'd be really useful, because I can keep special care at the most common user errors.
I'll try to get them. If I'm not able to get them all, I recommend you to search for examples in my own account: I usually test a lot of files so it's probable that I have most of the errors in my account. :-)
Nothing to be designed here. The window supports better error reporting.
Thanks! Just wanted to ask because don't know about its new design.
I'm adding the cases I'm facing today to the first post.
As talked via Slack, another suggestion regarding to the import process: warn the user from the editor if it's uploading an uncompressed file, advising that compressing the file will reduce the upload time.
I have just seen an encoding error without explanation in the UI, wasn't that be added in this issue? I'm seeing "Encoding::InvalidByteSequenceError" but the system is not raising it. I have a file that I can share in private if needed.
@iriberri not all encoding errors are catched in the same place or in the same way. Open a new issue (with the trace if you have it) and send me the file.
Some basic ones, like for example: encoding, projections, columns with repeated names... we could retrieve the most frequent ones from the metrics and start with them.
Please @juanignaciosl let me know if there's anything that I could help you with. :smile:
cc/ @miguelarias
Repeated columns (not really, but strings are trimmed)
Table without a header column (a float number is being detected as header)