샘플
nimble_pool 1.1.0: Check a resource out of a NimblePool and survive the failure paths: what the checkout function must return, which failures the pool recovers from, and which one silently leaks a worker
검증된 샘플 — hex nimble_pool 1.1.0: Check a resource out of a NimblePool and survive the failure paths: what the checkout function must return, which failures…
sha256:b9a321085b5992dc0c641045e8b697e67dbb23c7f9958ea2d4e0b145d1a2f486
이 네트워크가 제공하는 것은 하나입니다. 빌드되는 샘플. 샌드박스에서 돌리고 서명된 영수증을 보관합니다. 등급을 매기지 않고 무엇도 보증하지 않습니다 — 같은 코드가 당신 환경에서 빌드되는지는 측정한 적이 없습니다.
통과한 계약 영수증을 낸 서로 다른 서명 키의 수입니다. 하나면 작성자 혼자이고, 둘 이상이면 다른 사람도 빌드했다는 뜻입니다. 키는 스스로 만드는 것이고 뒤에 등록된 신원이 없으므로, 세는 것은 사람이 아니라 키입니다.
MIT-0
실행 증거
선언된 환경과 서명된 실행을 분리해 두었습니다. 이 샘플이 무엇을 어디서 실행했는지 그대로 볼 수 있습니다.
- 증거 기준
- 서명된 컨트랙트 통과
- 검증 영수증
- 1
- 빌드한 서명 키
- 1
선언된 환경
elixir 1 linux x64 elixir 1 elixir mix
검증 실행 환경
| 환경 | 컨트랙트 | 단계 | 실행일 |
|---|---|---|---|
| elixir 1 · linux alpine/x64 · docker ed25519:a2ec939a4c60e243 | PASS | compile:PASS · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · hex@1 |
2026-08-14 |
케이스
HOW- 목표
- Check a resource out of a NimblePool and survive the failure paths: what the checkout function must return, which failures the pool recovers from, and which one silently leaks a worker
- 심벌
-
- NimblePool.start_link
- NimblePool.checkout!
- NimblePool.update
- NimblePool.child_spec
- NimblePool.init_pool
- NimblePool.init_worker
- NimblePool.handle_checkout
- NimblePool.handle_checkin
- NimblePool.handle_update
- NimblePool.handle_cancelled
- NimblePool.terminate_worker
- 환경
- elixir 1
- 생성일
- 2026-08-14T20:12:13Z
컨트랙트
- assert :pool_size defaults to 10 rather than System.schedulers_online(), by counting exactly ten init_worker callbacks at start_link and no eleventh
- assert lazy: true starts no workers at all and builds exactly one on the first checkout
- assert the checkout! function body runs in the CLIENT process, and that the from it receives is {pool_pid, ref} carrying the POOL's pid, unlike GenServer.handle_call/3 where from carries the caller's
- assert checkout! returns the first element of the two-tuple and only handle_checkin/4 ever sees the second
- assert the asynchronous check-in does not race a re-checkout: twenty-five sequential checkouts against a one-worker pool all succeed
- assert raising inside the checkout! function is the recoverable failure: handle_cancelled(:checked_out) then terminate_worker(:error, ...) then a replacement init_worker, with handle_checkin skipped
- assert returning a value that is not a two-tuple raises {:try_clause, value} and silently leaks the worker: no handle_cancelled, no terminate_worker, no replacement, and every later checkout on that pool exits :timeout
- assert the leaked worker is reclaimed only when the calling process itself dies, which is when the pool's monitor fires handle_cancelled(:checked_out) and terminate_worker(:DOWN, ...)
- assert {:skip, exception, pool_state} from handle_checkout/4 raises that exception in the client while leaving the worker checked in and serving the next call, terminating nothing
- assert {:remove, reason, pool_state} from handle_checkout/4 retries the same checkout against another worker, so a remove keyed on the command destroys and rebuilds more workers than the pool size and the caller only ever sees its own checkout timeout
- assert a caller that times out while still queued cancels as :queued and tears down nothing, while a caller killed holding a worker cancels as :checked_out with terminate_worker reason :DOWN
- assert NimblePool.update/2 is called from inside the checkout! function with from, routes to handle_update/3, and replaces the worker_state that handle_checkin/4 later receives while the client_state passes through unchanged
파일
- csx.json
- lib/csx_nimble_pool/churn_worker.ex
- lib/csx_nimble_pool/instrumented_worker.ex
- mix.exs
- mix.lock
- test/contract_test.exs
- test/test_helper.exs