PR 3327 shipped beads-side crash recovery that string-matches the dolt server log tail and, on a start failure, backed up and REINITIALIZED the .dolt directory in place automatically — a destructive path that was never reproduced locally and violates the charter storage boundary. The server start path now only detects the GH#3290 condition (signature in log tail + provably-empty journal/oldgen) and points at bd doctor --fix in the start-failure error. The repair itself moved behind an explicit doctor fix: a new 'Corrupt Manifest' check reports affected databases, and the fix dispatcher runs the backup+reinit only after the user's per-fix confirmation prompt (or --yes). Both log signatures verified present in the pinned dolt source (store/datas/database_common.go, store/nbs/journal_record.go ErrJournalDataLoss). Driver-side migration of the log scraping tracked as bd-qo452. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| dirty_state_test.go | ||
| doltserver.go | ||
| doltserver_test.go | ||
| doltserver_unix.go | ||
| doltserver_windows.go | ||
| lifecycle_integration_test.go | ||
| logrotate.go | ||
| logrotate_test.go | ||
| manifest_recovery.go | ||
| manifest_recovery_test.go | ||
| port_race_test.go | ||
| servermode.go | ||
| socket_integration_test.go | ||