Skip to content

feat: skip detonation by default, fix rescan body and OS values - #26

Merged
ayoubfaouzi merged 3 commits into
mainfrom
feat/skip-detonation
Aug 3, 2026
Merged

feat: skip detonation by default, fix rescan body and OS values#26
ayoubfaouzi merged 3 commits into
mainfrom
feat/skip-detonation

Conversation

@ayoubfaouzi

Copy link
Copy Markdown
Member
  • fix: deduplicate identical files extracted from archives

- Clarify that -d/--enableDetonation opts into sandbox detonation;
  skip_detonation=true is sent by default (help text said the opposite)
- Flatten the rescan JSON body: the backend binds FileScanRequest directly,
  so os/timeout nested under scan_cfg were silently ignored
- Use the platform's canonical OS identifier windows-10-x64 (was win-10,
  which the backend accepts but the web UI doesn't recognize)
The backend records every archive entry in derived_files but only scans
each unique hash once. The CLI created one polling row per entry and, on
rescan paths, submitted duplicate hashes twice. Dedupe children by SHA256
before rescanning/polling and show the duplicate count in the archive row.
@ayoubfaouzi
ayoubfaouzi merged commit 20de724 into main Aug 3, 2026
3 checks passed
@ayoubfaouzi
ayoubfaouzi deleted the feat/skip-detonation branch August 3, 2026 06:12
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