CodeSampleX

Sample

Demonstrate that Pool timeout acts as a single-shot deadlock timer rather than a recurring per-request queue wait limit, leaving subsequent requests on a saturated pool unmonitored.

sha256:33e82e017667acd6225ae23ba25e976a68f31b30b6b8f9a268df089f59cc4482

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
dart
Operating system
linux
Architecture
x64
Runtime
dart
Language
dart
Package manager
pub

Verification-run environments

Execution context
dart 3
Operating system
linux debian · glibc
Architecture
x64
Runtime
dart 3
Language
dart
Package manager
pub
Execution
container · docker

CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · pub@1 · 2026-08-17

Case

Goal
Demonstrate that Pool timeout acts as a single-shot deadlock timer rather than a recurring per-request queue wait limit, leaving subsequent requests on a saturated pool unmonitored. HOW
Packages
pool 1.5.1
Environment
dart
Created
2026-08-17T15:02:39Z

Commonly assumed

Configuring Pool with a timeout duration causes every queued resource request to time out after waiting for that duration while the pool is at capacity.

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

Contract

Files

Download the source artifact (tar.gz)

Origin Seeder

csx-seed

Verification receipts