A production host's archied logs this on every start:
WARN config file has unrecognised keys; check for typos
keys=["indexing","indexing.db_path","indexing.index_dir"]
The workspace codesearch indexer was deleted in 2a4e7647, so the section is dead, but the host's ~/.config/archie/config.toml still carries it.
config.example.toml is clean and has no [indexing] section, so this is a host-config leftover rather than a template problem.
Effect: a permanent warning that names nothing actionable, on every boot. An operator learns to ignore it -- which is the real cost, because that same warning is the one that would report a genuine typo later.
Fix: drop [indexing] (and its index_dir / db_path keys) from the host's config.
The host is recorded in the operator's memos instance, not here: beads must not carry production instance detail.
Imported from beads archie-core-0h3w · GitHub #1161 · type bug · priority P3 · created 2026-09-23
A production host's archied logs this on every start:
WARN config file has unrecognised keys; check for typos
keys=["indexing","indexing.db_path","indexing.index_dir"]
The workspace codesearch indexer was deleted in 2a4e7647, so the section is dead, but the host's ~/.config/archie/config.toml still carries it.
config.example.toml is clean and has no [indexing] section, so this is a host-config leftover rather than a template problem.
Effect: a permanent warning that names nothing actionable, on every boot. An operator learns to ignore it -- which is the real cost, because that same warning is the one that would report a genuine typo later.
Fix: drop [indexing] (and its index_dir / db_path keys) from the host's config.
The host is recorded in the operator's memos instance, not here: beads must not carry production instance detail.
---
_Imported from beads `archie-core-0h3w` · GitHub #1161 · type bug · priority P3 · created 2026-09-23_
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.
A production host's archied logs this on every start:
WARN config file has unrecognised keys; check for typos
keys=["indexing","indexing.db_path","indexing.index_dir"]
The workspace codesearch indexer was deleted in
2a4e7647, so the section is dead, but the host's ~/.config/archie/config.toml still carries it.config.example.toml is clean and has no [indexing] section, so this is a host-config leftover rather than a template problem.
Effect: a permanent warning that names nothing actionable, on every boot. An operator learns to ignore it -- which is the real cost, because that same warning is the one that would report a genuine typo later.
Fix: drop [indexing] (and its index_dir / db_path keys) from the host's config.
The host is recorded in the operator's memos instance, not here: beads must not carry production instance detail.
Imported from beads
archie-core-0h3w· GitHub #1161 · type bug · priority P3 · created 2026-09-23