Skip to content

Record evidence-relative source paths for directory and single-file inputs - #222

Merged
abrignoni merged 1 commit into
mainfrom
fix/seeker-relative-source-path
Sep 19, 2026
Merged

abrignoni merged 1 commit into
mainfrom
fix/seeker-relative-source-path

Conversation

@abrignoni

Copy link
Copy Markdown
Owner

Records an evidence-relative path in file_infos for directory and single-file inputs, the form the zip, tar, raw image and iVa seekers already record. The value reaches the LAVA file list, every media source path and any artifact that reads file_infos, so a report from a directory input no longer carries the examiner's own folder layout.

Also fixes the directory seeker's staged paths, which lost their first character when the input path ended in a separator and lost every dot when the input was a bare dot.

The new test also runs on the Windows smoke job, which covers the extended-length prefix the entry points add there.

Same change as abrignoni/iLEAPP#2215, for abrignoni/iLEAPP#2057.

Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com

…nputs

FileSeekerDir recorded the absolute path on the examiner's machine in
file_infos and FileSeekerFile its absolute input path, while the zip, tar,
raw image and iVa seekers record where the file sits in the evidence. The
value reaches the LAVA _file_path_list, every media item's source_path and
any artifact that reads file_infos, so the same column meant two different
things depending on the input type, and a directory input published the
examiner's folder layout.

Both now record the evidence form: the path relative to the input
directory with forward slashes, or the file name for a single-file input.
The case-variant tag already hashed that spelling, so tagged copies keep
their names.

The directory seeker also built each staged path by slicing the input path
off the front of the match and dropping one more character. An input
ending in a separator lost the first letter of every staged path, and an
input of '.' lost every dot. os.path.relpath handles both, and the
extended-length prefix the entry points add on Windows.

The new test runs the real seekers against a small tree with the input
given as an absolute path, with a trailing separator, relative, and as
'.'. On Windows it also tries the extended-length prefix, and the Windows
smoke job now runs it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@abrignoni
abrignoni merged commit 3b0bec6 into main Sep 19, 2026
8 checks passed
@abrignoni
abrignoni deleted the fix/seeker-relative-source-path branch September 19, 2026 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant