Recordshexnimble_pool1.1.0NimblePool.handle_info
Published samples
- nimble_pool 1.1.0: Prove that NimblePool.handle_info/2 is a per-worker callback that receives (message, worker_state) and must return {:ok, new_worker_state}, not the GenServer shape {:noreply, state}, and that the wrong return shape crashes the entire pool process 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. HOWNimblePool.handle_infoelixir MIT-0 · 2026-08-17
Compatibility matrix
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| elixir 1 · elixir · mix · linux musl · docker
Verified: CONTRACT 2✓
|
MEDIUM | 0 | 2 | 100% | 0 · 2✓ | 2026-08-18 |
snapshot · 2026-08-30
Failure clusters
No failure clusters observed.