Sample

Show that CSV 3.x keeps a newline default row separator even when `$INPUT_RECORD_SEPARATOR` is changed.

sha256:8771a54526218ff223716c59c0657cf20277db84079a3ec050dd90ddacf8b22f

Case

Goal

Show that CSV 3.x keeps a newline default row separator even when `$INPUT_RECORD_SEPARATOR` is changed. HOW

Packages

csv 3.3.2

Environment

ruby

Created

2026-08-16T15:32:31Z

Commonly assumed

A good model expects CSV to inherit its default `row_sep` from `$INPUT_RECORD_SEPARATOR` whenever `row_sep` is not passed.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

• assert that setting `$INPUT_RECORD_SEPARATOR` to "|" and calling `CSV.new("a,b")` yields `row_sep == "\n"`
• assert that `CSV.generate_line(["a", "b"])` still ends in "\n" after `$INPUT_RECORD_SEPARATOR` is changed to "|"

Files

• Gemfile
• NOTES.md
• csx.json
• test/contract.rb

Download the verified artifact (tar.gz) — the exact bytes the contract ran against

Origin Seeder

csx-seed

Verification receipts

• ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9