Too many missing warnings

[adienes]

┌ Warning: thread = 1 warning: only found 9 / 11 columns around data row: 113. Filling remaining columns with `missing`
└ @ CSV ~/.julia/packages/CSV/b8ebJ/src/file.jl:576
┌ Warning: thread = 1 warning: only found 9 / 11 columns around data row: 114. Filling remaining columns with `missing`
└ @ CSV ~/.julia/packages/CSV/b8ebJ/src/file.jl:576
┌ Warning: thread = 1 warning: only found 9 / 11 columns around data row: 115. Filling remaining columns with `missing`
└ @ CSV ~/.julia/packages/CSV/b8ebJ/src/file.jl:576
┌ Warning: thread = 1 warning: only found 9 / 11 columns around data row: 116. Filling remaining columns with `missing`
└ @ CSV ~/.julia/packages/CSV/b8ebJ/src/file.jl:576
┌ Warning: thread = 1 warning: only found 9 / 11 columns around data row: 117. Filling remaining columns with `missing`
└ @ CSV ~/.julia/packages/CSV/b8ebJ/src/file.jl:576
┌ Warning: thread = 1 warning: only found 9 / 11 columns around data row: 118. Filling remaining columns with `missing`
└ @ CSV ~/.julia/packages/CSV/b8ebJ/src/file.jl:576
┌ Warning: thread = 1 warning: only found 9 / 11 columns around data row: 119. Filling remaining columns with `missing`
└ @ CSV ~/.julia/packages/CSV/b8ebJ/src/file.jl:576
┌ Warning: thread = 1 warning: only found 9 / 11 columns around data row: 120. Filling remaining columns with `missing`
└ @ CSV ~/.julia/packages/CSV/b8ebJ/src/file.jl:576
┌ Warning: thread = 1 warning: only found 9 / 11 columns around data row: 121. Filling remaining columns with `missing`
└ @ CSV ~/.julia/packages/CSV/b8ebJ/src/file.jl:576
┌ Warning: thread = 1 warning: only found 9 / 11 columns around data row: 122. Filling remaining columns with `missing`
└ @ CSV ~/.julia/packages/CSV/b8ebJ/src/file.jl:576

one warning at most is sufficient. definitely not one per row. honestly I would expect this as default behavior so I'd be ok if it didn't warn at all

[jariji]

I would rather get a failure by default.

[quinnj]

You can pass maxwarnings=1 if you want

[adienes]

@quinnj it's great to have that level of control, but I intended this issue to be about default behavior. Respectfully, I do not think the current behavior is a reasonable default