Sample
CommandRunner concurrent execution mutates active command argResults across async await points
sha256:25ac71b73fda96d8b3fb6be3afaadce8383fa67d77da5e164dd34c5e6e334d4c
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- CommandRunner concurrent execution mutates active command argResults across async await points HOW
- Packages
- args 2.7.0
- Environment
- dart
- Created
- 2026-08-17T02:03:23Z
Commonly assumed
Concurrent invocations of CommandRunner.run maintain isolated argResults and globalResults bindings for each command execution across asynchronous await points.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Calling CommandRunner.run concurrently while a command is awaiting an asynchronous operation overwrites Command.argResults and Command.globalResults mid-execution with the newly parsed values.
- argResults['job'] is 'A' before await, but changes to 'B' after await in the first invocation.
- globalResults['env'] is 'staging' before await, but changes to 'production' after await in the first invocation.
Files
- NOTES.md
- csx.json
- pubspec.lock
- pubspec.yaml
- test/contract.dart
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- dart 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · pub@1 · 2026-08-16 · ed25519:d91480838ac982c9