You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug: InterruptError — All fibers interrupted when InstanceStore.dispose races with Agent.list #32755
When an HTTP request triggers Agent.list (which reads agent configuration from the filesystem via ScopedCache.get), and at the same time another request triggers InstanceStore.dispose, the ScopedCache invalidation interrupts all in-flight lookup fibers, producing InterruptError: All fibers interrupted without error.
This error propagates up to the HTTP response and reaches the Telegram Bot as a session.promptAsync failure.
Stack trace
InterruptError: All fibers interrupted without error
at FileSystem.up (B:/~BUN/root/chunk-pcf2w4yn.js:2:18581)
at FileSystem.up (definition) (B:/~BUN/root/chunk-ewqah108.js:16:23248)
at Agent.state (B:/~BUN/root/chunk-ae5jadfy.js:2:4743)
at Agent.state (definition) (B:/~BUN/root/chunk-10rcnd8y.js:171:805)
at Agent.list (B:/~BUN/root/chunk-nv7cdy3k.js:2:207057)
at Agent.list (definition) (B:/~BUN/root/chunk-10rcnd8y.js:171:5293)
at InstanceHttpApi.agent (B:/~BUN/root/chunk-nv7cdy3k.js:2:79248)
at InstanceHttpApi.agent (definition) (B:/~BUN/root/chunk-nv7cdy3k.js:2:207000)
at Server.listen (B:/~BUN/root/chunk-nv7cdy3k.js:3:46713)
at Server.listen (definition) (B:/~BUN/root/chunk-nv7cdy3k.js:3:46836)
Root cause
1. Race condition in InstanceState.make + disposeMiddleware
packages/opencode/src/effect/instance-state.ts line 38 registers a disposer that invalidates the ScopedCache when the instance is disposed. If a concurrent HTTP request is in the middle of Agent.list → ScopedCache.get → lookup → Agent.state (reading files via FileSystem.up), the invalidation closes the Effect scope and interrupts all child fibers.
Activity
github-actions commentedon Aug 17, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.