Sample
csv 3.3.2: Show that CSV 3.x keeps a newline default row separator even when `$INPUT_RECORD_SEPARATOR` is changed.
Verified sample for gem csv 3.3.2: Show that CSV 3.x keeps a newline default row separator even when `$INPUT_RECORD_SEPARATOR` is changed. The contract ran…
sha256:8771a54526218ff223716c59c0657cf20277db84079a3ec050dd90ddacf8b22f
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 1
Declared environment
ruby linux x64 ruby ruby bundler
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| ruby 3 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-16 |
| ruby 3 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 | SKIPPED | compile:SKIPPED · contract:SKIPPED · load:SKIPPED · resolve:FAIL CONTAINER_RUN · rubygems@1 |
2026-08-18 |
Case
HOW- Goal
- Show that CSV 3.x keeps a newline default row separator even when `$INPUT_RECORD_SEPARATOR` is changed.
- Packages
- Symbols
-
- CSV.new
- Environment
- ruby
- Created
- 2026-08-16T15:32:31Z
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