Repository navigation
History keeps the pictures shown last on Featherframe Cloud (W-1009) - #359
Merged
wr merged 1 commit intoOct 7, 2026
Conversation
History pruned frames/history/*.png by file time. A Cloud start unpacks bundles/history.tar in path order, so the times followed the ETag's hex and each commit pruned the lowest ETag, not the oldest picture: its full-size JPEG was encoded and uploaded again whenever the species came back, and the History card lost recent pictures. History now keeps the newest 24 distinct ETags of the render log, and prunes every other PNG and JPEG (one still at the front door too). Waiting plates keep the last 8 drawn by a kv record, and a thumbnail is dropped by whatever replaces its image instead of compared by time. Refs: W-1009
wr
enabled auto-merge (squash)
October 7, 2026 04:46
wr
deleted the
wells/w-1009-history-keeps-the-pictures-shown-last-on-featherframe-cloud
branch
October 7, 2026 04:47
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
1 participant
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.
On Featherframe Cloud the History card lost recent pictures and kept older ones, and the server encoded and uploaded the same full-size JPEGs again and again. From 6 Oct 2026 10:00Z to 7 Oct 2026 04:00Z, Workers observability shows history JPEGs 5750a4a32140b91e, 159d7c9f9fc51bc8, 1a21d60ad4fee1c6, 5718f0b53e30c362 and 77c8c5edaeaa36f7 (all low hex) each PUT and then DELETEd 3–6 times.
Cause
_save_history_thumbprunedframes/history/*.pngby file time. On Cloud those PNGs travel inbundles/history.tar(W-985)._tarwritesmtime=0and_unpackwrites every file fresh at the start, in sorted path order. After each start the times follow the ETag's hex, so the next commit pruned the lowest ETag, not the oldest picture.What changes
<etag>.pngand.jpggoes, including a JPEG still at the front door with no PNG beside it._prune_views) were ordered by time the same way: a start fetches them in parallel. They now keep the last 8 drawn, by a kv record (waiting_views).thumbs.thumb_forcompared a thumbnail's time with its image's. After a start, an image fetched later looked newer and was decoded again for nothing, and an image replaced in an earlier run kept its stale thumbnail. A thumbnail is now drawn once, and whatever replaces its image drops it: a regenerated or restored illustration, the day's collage redrawn._tarstays deterministic: its hash is what keeps an unchanged archive from being sent again.Verified
make test: 1241 passed, 2 skipped.Left
Refs W-1009