Repository navigation
fix: age out bytes-shown markers like the other three kinds (#469) - #471
Merged
Merged
Conversation
session-start-hook.sh named only vocab-shown, path-shown and edited in both the resume cleanup and the seven-day age-out, so the per-session bytes-shown markers jit_shown_mark writes (#389) were kept forever. Section K of test-session-markers.sh backdates all four kinds. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #469.
session-start-hook.shcleared and aged outvocab-shown,path-shownandeditedmarkers only.bytes-shown-<session>.txt(written byjit_shown_mark, #389) was kept forever.bytes-shownadded to the resumerm -f/rmdirlists and to the perl age-out patterntests/test-session-markers.sh: all four kinds backdated, fresh ones of another session kept, own session cleared. vocab-shown is the control. Red on the two bytes-shown legs before the fix, 66/66 after.PRIVACY.md: up to 0.16.0 they were not aged out, from the next release they are. The policy URL reads main and installed users are still on 0.16.0, so it says both.changelog.d/469.fixed.bytes-shown-age-out.md🤖 Generated with Claude Code
[AI-generated]