script hangs when mistakingly using Extractors.CSV instead of Extractors.TSV

USQL script on ADLA were hanging indefinitely, until we realized that we had setup the wrong extractor (CSV instead of TSV) on a `.tsv` file.
Sure it is our fault, moreover because we specified `silent: true`.
Still, I would expect the script to complete (and not hang), but not extract any record (because they would all fail validation since there would be no comma on the rows).
What do you think?