Skip to content

Add an explicit error message and test for invalid-encoding files at the CSV Manifest level

rfb11 requested to merge csv-manifest-invalid-byte-sequence into main

This makes it so if you ingest e.g. a UTF-8 file with a UTF-16 BOM, you'll get an error message like: Invalid byte sequence in CSV manifest (check file encoding): incomplete "\n" on UTF-16BE

Merge request reports