boot applies control-plane values over the file config once, at startup:
loadRuntimeConfig (internal/app/archied/control_plane.go:12) is called from
main.go:380 and gateway.go:132 and nowhere else.
The SIGHUP reload callback (internal/app/archied/bootstrap.go:1394) re-resolves
the file document and publishes doc.Config. It never re-reads the control
plane. So a reload silently reverts every database-owned setting to its file
value, and they stay reverted until the process restarts: providers, model role
assignments, repository policies, chat/channel settings, scheduling policy,
tool and plugin settings, and container runtime policies.
Nothing reports it. The reload logs "config reloaded" and
changedNonReloadableFields compares the old published config against the new
file document, so the regression can even look like an intentional change.
The fix already has a precedent three lines above it: the same callback
re-applies applyModelCatalog because "publishing the raw reloaded document
would drop them from the running config even though the file is unchanged."
That is this bug exactly, for catalog providers, solved for catalog providers
only. Re-apply the control-plane layer in the same place.
Found while correcting docs/architecture/configuration.md for archie-core-b7dn.
Introduced with the control plane in 924b02a1, not by the overlay deletion.
Close reason
Fixed in 9af013eb (2026-09-21): reloadConfig re-applies the control-plane layer via b.runtimeConfig before publishing, and a State Store that cannot answer fails the reload instead of reverting to file values.
Imported from beads archie-core-ju85 · GitHub #1051 · type bug · priority P1 · created 2026-09-21 · closed 2026-09-26
boot applies control-plane values over the file config once, at startup:
loadRuntimeConfig (internal/app/archied/control_plane.go:12) is called from
main.go:380 and gateway.go:132 and nowhere else.
The SIGHUP reload callback (internal/app/archied/bootstrap.go:1394) re-resolves
the file document and publishes doc.Config. It never re-reads the control
plane. So a reload silently reverts every database-owned setting to its file
value, and they stay reverted until the process restarts: providers, model role
assignments, repository policies, chat/channel settings, scheduling policy,
tool and plugin settings, and container runtime policies.
Nothing reports it. The reload logs "config reloaded" and
changedNonReloadableFields compares the old published config against the new
file document, so the regression can even look like an intentional change.
The fix already has a precedent three lines above it: the same callback
re-applies applyModelCatalog because "publishing the raw reloaded document
would drop them from the running config even though the file is unchanged."
That is this bug exactly, for catalog providers, solved for catalog providers
only. Re-apply the control-plane layer in the same place.
Found while correcting docs/architecture/configuration.md for archie-core-b7dn.
Introduced with the control plane in 924b02a1, not by the overlay deletion.
### Close reason
Fixed in 9af013eb (2026-09-21): reloadConfig re-applies the control-plane layer via b.runtimeConfig before publishing, and a State Store that cannot answer fails the reload instead of reverting to file values.
---
_Imported from beads `archie-core-ju85` · GitHub #1051 · type bug · priority P1 · created 2026-09-21 · closed 2026-09-26_
sam
added the highbug labels 2026-10-27 13:40:16 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
boot applies control-plane values over the file config once, at startup:
loadRuntimeConfig (internal/app/archied/control_plane.go:12) is called from
main.go:380 and gateway.go:132 and nowhere else.
The SIGHUP reload callback (internal/app/archied/bootstrap.go:1394) re-resolves
the file document and publishes doc.Config. It never re-reads the control
plane. So a reload silently reverts every database-owned setting to its file
value, and they stay reverted until the process restarts: providers, model role
assignments, repository policies, chat/channel settings, scheduling policy,
tool and plugin settings, and container runtime policies.
Nothing reports it. The reload logs "config reloaded" and
changedNonReloadableFields compares the old published config against the new
file document, so the regression can even look like an intentional change.
The fix already has a precedent three lines above it: the same callback
re-applies applyModelCatalog because "publishing the raw reloaded document
would drop them from the running config even though the file is unchanged."
That is this bug exactly, for catalog providers, solved for catalog providers
only. Re-apply the control-plane layer in the same place.
Found while correcting docs/architecture/configuration.md for archie-core-b7dn.
Introduced with the control plane in
924b02a1, not by the overlay deletion.Close reason
Fixed in
9af013eb(2026-09-21): reloadConfig re-applies the control-plane layer via b.runtimeConfig before publishing, and a State Store that cannot answer fails the reload instead of reverting to file values.Imported from beads
archie-core-ju85· GitHub #1051 · type bug · priority P1 · created 2026-09-21 · closed 2026-09-26