Sample
Handle CSV::InvalidEncodingError inheriting from MalformedCSVError rather than EncodingError, ArgumentError on nil inputs, and unclosed quotes despite liberal_parsing in CSV
sha256:6c5ffc8a79396c5e831eed2edeefc0ee240d543d3937dad970365842c019aef5
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Handle CSV::InvalidEncodingError inheriting from MalformedCSVError rather than EncodingError, ArgumentError on nil inputs, and unclosed quotes despite liberal_parsing in CSV HOW
- Packages
- csv 3.3.2
- Environment
- ruby
- Created
- 2026-08-16T15:29:41Z
Commonly assumed
CSV::InvalidEncodingError inherits from Ruby core's EncodingError, and liberal_parsing: true suppresses unclosed quote errors.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- CSV::InvalidEncodingError inherits from CSV::MalformedCSVError and RuntimeError rather than EncodingError, so rescue EncodingError fails to catch byte sequence errors during parsing.
- assert CSV.parse with invalid byte sequences raises CSV::InvalidEncodingError reporting the 1-based line_number
- assert CSV.parse and CSV.parse_line raise ArgumentError with message 'Cannot parse nil as CSV' when passed nil
- assert CSV.parse_line on an empty string returns nil whereas CSV.parse returns an empty array
- assert CSV.parse with liberal_parsing: true allows unescaped quotes but still raises CSV::MalformedCSVError on unclosed quotes
- assert CSV::MalformedCSVError inherits from RuntimeError and attaches line_number on parse errors
Files
- Gemfile
- NOTES.md
- csx.json
- test/contract.rb
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9