Skip to content

Import should not report failure after DB replacement when sidecar cleanup fails #3125

Description

@Widthdom

Problem

ReplaceImportedDatabase moves the imported temp database into place and then deletes SQLite sidecars. If sidecar cleanup throws after the move, the outer import flow can report the import as failed even though the main database has already been replaced.

Evidence

  • src/CodeIndex/Cli/ExportImportCommandRunner.cs around ReplaceImportedDatabase

Suggested direction

Separate post-replacement sidecar cleanup failures from the database replacement outcome. Either make sidecar cleanup best-effort after a successful move, or report a partial-success state that does not imply the original DB is still intact.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions