Repository navigation
HMR profile recomposition leaves Desktop with no active "sessionController" — all session RPCs fail with gateway/service-unavailable until app restart #10237
Replies: 1 comment
Another reproduction:
|
Another reproduction:
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Environment
desktop(bundles:dsh-base,dsh-web-app, plus several third-party/local plugin bundles)dsh-base:disabled: !!js "!ctx.get('profileContext')")Summary
While a session is running, editing
~/.dsh/cordis.patch.ymltriggers the expected HMR profilerecomposition: the running turn is aborted with
{"kind":"aborted","reason":{"kind":"disposed"}}about 2 s after the write (the HMR
awaitWriteFinishwindow). But the recomposition does notend in a usable state: the typert gateway stays up while no active
sessionControllerservice isregistered, so every
session/createandsession/promptcall keeps failing withgateway/service-unavailableuntil the app is restarted. The exact same config boots fine on acold start.
Steps to reproduce (observed twice, 2026-10-19)
~/.dsh/cordis.patch.yml(first occurrence: add asession-query-sqliteoverride; second occurrence: remove it — i.e. any write is enough).disposed.(Observed continuously for ~6 minutes in the first occurrence.)
Errors
Evidence (redacted structural records from session logs)
Expected vs actual
is reported as "restart required" (v0.2.1-rc.1 release notes: hot-reloadable plugins apply
directly, non-hot-reloadable ones prompt for a restart).
active,
sessionControllernever (re)registers, there is no prompt/rollback, and the onlyrecovery is a full app restart. Desktop does not persist host-side logs, so users cannot see
which entry failed to activate.
Notes / hypotheses
typert-gateway(dsh-base) andsession-controller(dsh-web-app) are rows of the same recomposedtree; after recomposition the gateway is active but
sessionControlleris not. This looks like thein-place recompose failing to activate the session-controller entry, combined with the documented
failure policy (dsh-hmr README: after eviction, a replacement that fails to import/start is an
activation failure; the operation fails and its old code no longer runs).
activation-failure trigger, because host-side logs are not persisted.
Asks
sessionControllerafter an HMR recomposition intendedbehavior, or a bug in the recompose/activation-failure path?
failed to activate?
on activation failure, instead of leaving the tree partially active?
- id: hmr/disabled: true) in the profilepatch?
Workaround we are using
Disabling HMR in the desktop profile patch, so patch edits simply require an app restart
(
- id: hmr+disabled: true).All reactions