Check which profile the after-play dialog and the save list name after a switch #105
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#105
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?
Things an agent noticed while taking user-guide screenshots on 0.9.7 (Ubuntu VM, Grounded with profiles Vanilla, Modded and Heavy mods, Heavy mods made while Vanilla was loaded). None is confirmed yet; reproduce each in a test or on the VM and fix what is wrong:
Investigated on branch issue-105-session-attribution. (1) was a real bug: a profile made with New profile starts its saves on the loaded profile's point, so Replace named the other profile's snapshot; Replace now offers only a snapshot the played profile owns (as History attributes it), and a profile with none gets Keep and Not now. (2) is intended: a profile made from another offers the saves it started with (#87). (3) did not reproduce: SavePoint compares content, and identical bytes with a new time count as unchanged in the engine, the capture count and the launch flow. The likeliest cause on Linux is a mode change (a game or script recreating save files with other permissions), which git counts as a change even with the same bytes; if it shows again,
git --git-dir=<storage>/<game>/external.git --work-tree=<saves> diff --raw HEADwill tell, and whether saves folders should ignore permission bits is then a decision to make. (4) did not reproduce in a journey that builds the same state; if it shows again, the log times of the capture job and the profile row reload will say whether a reload ran before the snapshot landed.