johno/beads
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(daemon): use capabilities check instead of blanket Dolt block

Browse Source 
The daemon startup was blocking ALL Dolt backends, but Dolt server mode
actually supports multi-process access. Now checks SingleProcessOnly
capability like the guard function does, allowing daemon start with
Dolt server mode while still blocking embedded Dolt mode.

This silences the "DAEMON NOT SUPPORTED WITH DOLT BACKEND" warning
when using dolt_mode: "server" in the configuration.

Fixes gt-b8ed44

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Executed-By: mayor
Role: mayor
This commit is contained in:
mayor
2026-01-25 18:29:50 -08:00
committed by gastown/crew/joe
parent 9b9ef9fdba
commit 45e89d3dd4
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
cmd/bd/daemon.go
View File

@@ -366,14 +366,16 @@ func runDaemonLoop(interval time.Duration, autoCommit, autoPush, autoPull, local
backend = configfile.BackendSQLite
}
// Daemon is not supported with dolt backend - refuse to start
if backend == configfile.BackendDolt {
errMsg := `DAEMON NOT SUPPORTED WITH DOLT BACKEND
// Daemon is not supported with single-process backends (e.g., embedded Dolt)
// Note: Dolt server mode supports multi-process, so check capabilities not backend type
cfg, cfgErr := configfile.Load(beadsDir)
if cfgErr == nil && cfg != nil && cfg.GetCapabilities().SingleProcessOnly {
errMsg := fmt.Sprintf(`DAEMON NOT SUPPORTED WITH %s BACKEND
The bd daemon is designed for SQLite backend only.
With dolt backend, connect directly to the dolt sql-server.
The bd daemon is designed for multi-process backends only.
With single-process backends, run commands in direct mode.
The daemon will now exit.`
The daemon will now exit.`, strings.ToUpper(backend))
log.Error(errMsg)
// Write error to file so user can see it without checking logs