Skip to content

DbPathResolver metadata probes should catch filesystem and path errors #3175

Description

@Widthdom

Finding

DbPathResolver best-effort metadata probes only catch SqliteException.

Evidence

  • TryReadMetaString
  • TryReadIndexedFileSamples
  • Both methods open/read SQLite metadata and catch only SqliteException.

Risk

Invalid paths, inaccessible files, URI/path normalization problems, IOException, UnauthorizedAccessException, or other path-related exceptions can escape from what should be a best-effort diagnostic path.

Suggested fix

Catch the expected filesystem/path exception families around the open/read probe, keep the operation best-effort, and preserve useful diagnostics without crashing higher-level resolution.

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