The Go back dialog's size estimate ignores files the switch will remove #86
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ethan-hann/SavePoint#86
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?
On Linux (0.9.5, VM checks round 2 on #3), Go back to an older snapshot said "About 3 bytes of files will be replaced" while the switch then removed a 600 MB file that the folder held. The estimate seems to compare the target with the loaded snapshot rather than with what the folders hold now, or it counts only files that are replaced and not files that are removed. A player deciding whether to go back should see the real amount of change. Check how the estimate is computed (likely the same path on Windows), and make it count added, replaced and removed files against the current contents.