[GH-ISSUE #5489] [Feature] Add a dry-run plan for artifact extraction #3342

New issue

Open

opened 2026-10-31 00:39:20 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:39:20 +00:00

Owner

Originally created by @jayykernel on GitHub (Oct 20, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/5489

Problem

Before extracting an archive into a destination directory, users may want to review the planned output paths, potential collisions, and approximate total output size without creating files.

Proposed change

Add an opt-in dry-run mode to artifact extraction that reuses the actual path-normalization and admission logic but performs no output writes.

Acceptance criteria

The plan lists the logical output paths and clearly marks unresolved/unsupported entries.
Destination collisions and unsafe paths are reported using the same rules as real extraction.
The command creates no destination files, staging directories, or sidecar artifacts.
Any byte totals are labeled as declared/observed estimates as appropriate, not guaranteed disk usage.
Tests compare dry-run decisions with real extraction on safe fixtures, path collisions, and invalid names.

This is a workflow-safety enhancement; no current extraction defect is alleged.

Originally created by @jayykernel on GitHub (Oct 20, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/5489 ### Problem Before extracting an archive into a destination directory, users may want to review the planned output paths, potential collisions, and approximate total output size without creating files. ### Proposed change Add an opt-in dry-run mode to artifact extraction that reuses the actual path-normalization and admission logic but performs no output writes. ### Acceptance criteria - The plan lists the logical output paths and clearly marks unresolved/unsupported entries. - Destination collisions and unsafe paths are reported using the same rules as real extraction. - The command creates no destination files, staging directories, or sidecar artifacts. - Any byte totals are labeled as declared/observed estimates as appropriate, not guaranteed disk usage. - Tests compare dry-run decisions with real extraction on safe fixtures, path collisions, and invalid names. This is a workflow-safety enhancement; no current extraction defect is alleged.

bsakaguchi referenced this issue

2026-10-31 00:39:48 +00:00

[GH-ISSUE #5557] [Bug] Doctor waits past the Kuna version deadline when a descendant retains stdout #3385

bsakaguchi referenced this issue

2026-10-31 01:10:23 +00:00

[PR #3808] [MERGED] fix(apktool): own the version probe's process group and keep its timeout typed #5911