Sample
pino 9.6.0: Route pino logs via worker transports without dropping buffered output or triggering sonic-boom unready flush errors on process exit
Verified sample for npm pino 9.6.0: Route pino logs via worker transports without dropping buffered output or triggering sonic-boom unready flush errors on…
sha256:de5694752712703937b8768b58efc7c07dc1c87da5a4f209c635db1129789135
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.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
node linux x64 node node npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:ac1544ece1e22594 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-15 |
| node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-18 |
Case
HOW- Goal
- Route pino logs via worker transports without dropping buffered output or triggering sonic-boom unready flush errors on process exit
- Packages
- Symbols
-
- pino
- pino.transport
- pino.destination
- Environment
- node
- Created
- 2026-08-15T06:01:04Z
Contract
- assert pino.transport routes log output inside worker threads, bypassing main process.stdout.write interception
- assert logger.flushSync is undefined on logger instances and throws TypeError when invoked
- assert flushSync on an unready async destination throws sonic boom is not ready yet
- assert unflushed unready async file destinations trigger sonic boom not ready error on exit and drop logs
- assert synchronous file destinations persist logs immediately across process.exit
- assert worker transports automatically flush buffered logs across process.exit without data loss
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs