Sample
Prove that Faraday major version 2 dropped error classes from the `Faraday::Error` namespace
sha256:7f6e5d35059d0f67e60fc5bbff31fbccfe499e2e0a9880acdf9147bbf62ac72c
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Prove that Faraday major version 2 dropped error classes from the `Faraday::Error` namespace HOW
- Packages
- faraday 2.14.3
- Environment
- ruby
- Created
- 2026-08-16T17:32:41Z
Commonly assumed
A common v1-era expectation is that rescuing `Faraday::Error::ClientError` is still valid in Faraday 2.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
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
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