[BUG] Temporary-file cleanup remains armed after publication #5
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/boot-tool#5
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The Linux publisher left temporary-file cleanup armed after a successful rename.
Dropping the guard could then remove a new file created at the vacated name.
Reproduction
The regression control publishes its own file, recreates its old temporary name,
then drops the guard. It checks that the published output and the new file both
remain. This uses only test-owned files and requires no timing race.
Expected and actual behavior
Successful publication must disarm cleanup of the old name. The earlier guard
always attempted removal. A refused rename must still clean the unpublished
file without changing the destination.
Environment and identity
Affected:
3040a592e2a8745b0149ade92b5f4204321445b3, Linuxsrc/output.rs.Fixed in
220c364b7cdbdc20688211c18a7a2e1039f18cec; current head is50e22cb05ac2e2fd460ea83ca9c0e80fb484af98.Evidence and prior checks
Both new controls pass in debug and release; all 31 tests in each profile and
strict Clippy pass without warnings. The documented contract still requires a
stable parent directory, and destructor cleanup remains best effort.
Tracking
Related: #1 and #2.