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
Direct failures from a plugin's setup/effect are isolated by Plugin.load(...).pipe(Effect.exit). A transform failure is not isolated when State.batch defers its materialization until after that boundary:
setup registers a transform while Plugin.activate is batched.
The callback is stored without being invoked, so the plugin is marked active.
State.batch later materializes the transform and it throws.
The defect escapes into PluginSupervisor.activate.
The supervisor catches it before opening readiness:
yield*activate()if(observed===target)yield*ready.open.pipe(Effect.catchCause((cause)=>Effect.logError("failed to reload plugins",{ cause })))
The latch therefore remains closed and PluginSupervisor.flush never completes.
This is narrower than a direct setup throw or a PluginModule decode failure; both are already isolated.
The observed plugin used the obsolete commands.update() API. That plugin is invalid, but its transform failure should not block unrelated startup.
ERROR failed to reload plugins
TypeError: commands.update is not a function
ERROR Model catalog initialization timed out service=model.catalog
Impact
model.list times out waiting for plugin readiness. TUI location sync then rejects as a whole and displays Session location unavailable for an existing directory, with empty catalog pickers. Direct provider API requests still succeed.
Expected
Attribute the transform failure to its plugin and remove the failed registration.
Mark the plugin failed rather than active.
Settle readiness so healthy plugins, catalog reads, and location startup continue.
Do not present this service error as a missing directory.
changed the title [-]v2: V1 plugins in shared config brick catalog and show Session location unavailable[/-][+]v2: plugin setup throw bricks catalog and shows Session location unavailable[/+]on Aug 25, 2026
This was fixed in v2.0.0 by #47083: a deferred transform failure disables the responsible plugin, removes its registrations, and lets healthy plugins continue. Readiness is released after recovery rather than leaving catalog initialization blocked. If you still see this on v2, please open a new issue with the details.
Activity
[-]v2: V1 plugins in shared config brick catalog and show Session location unavailable[/-][+]v2: plugin setup throw bricks catalog and shows Session location unavailable[/+][-]v2: plugin setup throw bricks catalog and shows Session location unavailable[/-][+]v2: deferred plugin transform failure leaves readiness latch closed and bricks catalog[/+]neriousy commentedon Oct 20, 2026
This was fixed in v2.0.0 by #47083: a deferred transform failure disables the responsible plugin, removes its registrations, and lets healthy plugins continue. Readiness is released after recovery rather than leaving catalog initialization blocked. If you still see this on v2, please open a new issue with the details.