Rename GitProcessRegistry's persist flag and give each registry its own note entry #213

Closed
opened 2026-10-27 01:34:47 -05:00 by ethan-hann · 1 comment
Owner

GitProcessRegistry.Entry.Persist and the persist parameter mean "named in the running-git note", which reads as the opposite of GitRunner's SurvivesExit (a reclaim git that survives exit is added with persist: false). Rename it (for example Noted) so the two read the same way. Also, two registries on one runtime folder (tests restart a backend on the same folder) still overwrite each other's note while both run, because the note is one list per file; a close rewrites the survivor's gits, which hides it. Merge the writes or keep one entry per registry so neither drops the other's gits.

GitProcessRegistry.Entry.Persist and the persist parameter mean "named in the running-git note", which reads as the opposite of GitRunner's SurvivesExit (a reclaim git that survives exit is added with persist: false). Rename it (for example Noted) so the two read the same way. Also, two registries on one runtime folder (tests restart a backend on the same folder) still overwrite each other's note while both run, because the note is one list per file; a close rewrites the survivor's gits, which hides it. Merge the writes or keep one entry per registry so neither drops the other's gits.
ethan-hann added this to the Code Cleanup milestone 2026-10-27 01:34:47 -05:00
Author
Owner

Shipped in 0.9.17 (PR 227).

Shipped in [0.9.17](https://git.tortal.tech/ethan-hann/SavePoint/releases/tag/v0.9.17) (PR 227).
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ethan-hann/SavePoint#213
No description provided.