Sample
Prove adapter return-shape mismatches are not normalized into normal return tuples in Req.request/2.
sha256:a5649b752a3ed1b2bc12b4951b3d34587b35e7af8d5081134dbafd228edfba23
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Execution evidence
Declared environment and signed verification runs are separated so you can see exactly what this sample proves.
Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS
Declared environment
- Execution context
- elixir
- Operating system
- linux
- Architecture
- x64
- Runtime
- elixir
- Language
- elixir
- Package manager
- mix
Verification-run environments
- Execution context
- elixir 1
- Operating system
- linux alpine · musl
- Architecture
- x64
- Runtime
- elixir 1
- Language
- elixir
- Package manager
- mix
- Execution
- container · docker
CONTAINER_RUN · compile:PASS · contract:PASS · load:PASS · resolve:PASS · hex@1 · 2026-08-17
Case
- Goal
- Prove adapter return-shape mismatches are not normalized into normal return tuples in Req.request/2. HOW
- Packages
-
req 0.7.2
- Environment
- elixir
- Created
- 2026-08-17T04:45:27Z
Commonly assumed
Passing a malformed adapter to Req.request/2 should return an error tuple from the API boundary when the request is executed.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert RuntimeError is raised when an adapter returns a non-tuple shape instead of {request, response} or {request, exception}; Req.request/2 is used (not a stubbed plugin path).
- assert the RuntimeError message includes 'expected adapter to return {request, response} or {request, exception}'.
Files
- NOTES.md
- csx.json
- mix.exs
- mix.lock
- test/contract.exs
Download the source artifact (tar.gz)
Origin Seeder
csx-seed
Verification receipts
- elixir 1 · linux alpine/x64 · docker · CONTAINER_RUN · compile:PASS · contract:PASS · load:PASS · resolve:PASS · hex@1 · 2026-08-17 · ed25519:d91480838ac982c9