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
fix(doctor): stop emitting fresh-clone false positive in Dolt server mode (#3755)
When dolt_mode=server is configured but the Dolt server is unreachable
(TCP refused, TLS mismatch, auth failure), CheckFreshClone previously
fell through to the legacy "Fresh clone detected (N issues in
issues.jsonl, no database)" warning and recommended bd bootstrap.
In server mode the absence of a local Dolt directory is expected, so
the warning is a false positive and the recommended fix is wrong:
bd bootstrap won't help when the actual problem is connectivity or
credentials. The "fall through (FR-030)" comment misread FR-030, which
only requires that an unreachable server not panic the caller — not
that we silently degrade to a misleading message.
This change adds freshCloneServerUnreachableResult, which:
- identifies that we're in server mode and points at host:port,
- surfaces the underlying connection error in Detail for diagnostics,
- and recommends verifying server health, host/port, TLS, and
credentials rather than bd bootstrap.
CheckFreshClone now routes the unreachable branch through this helper
instead of falling through. The existing
TestCheckFreshClone_ServerModeUnreachable is updated to assert the new
behavior, and a new TestFreshCloneServerUnreachableResult adds direct
unit coverage for the helper, including a nil-error path.
0 commit comments