Sample
faraday 2.14.3: Prove that Faraday major version 2 dropped error classes from the `Faraday::Error` namespace
Verified sample for gem faraday 2.14.3: Prove that Faraday major version 2 dropped error classes from the `Faraday::Error` namespace. The contract ran on…
sha256:7f6e5d35059d0f67e60fc5bbff31fbccfe499e2e0a9880acdf9147bbf62ac72c
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 bundle
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| ruby 3 · linux debian/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
- Prove that Faraday major version 2 dropped error classes from the `Faraday::Error` namespace
- Packages
- Symbols
-
- Faraday::Error
- Faraday::ClientError
- Environment
- ruby
- Created
- 2026-08-16T17:32:41Z
Contract
- assert !Faraday::Error.const_defined?(:ClientError, false)
- assert_raise NameError when resolving Faraday::Error::ClientError
- assert Faraday::ClientError < Faraday::Error
Files
- Gemfile
- NOTES.md
- csx.json
- test/contract.rb