An undated list is refreshed when old, and a list not opened yet says "New" (#926) - #933
Merged
Merged
Conversation
… "New" (#926) Item 6 of #926, AutoGet's list expiry. With AUTO_REFETCH_LISTS on, a list whose bot's advert gives no date was never refreshed, however old: now it is fetched again once it is 14 days old, and the console says that was the reason. A dated bot is still refreshed only when its advert changes. Every fetch leaves the list unseen; opening it in the List Browser marks it seen, and the sidebar shows a "New" badge until then. Entries from before this are never marked. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AP6LSxkr4n9dMFNSNMogmW
This was referenced Sep 24, 2026
Ninja-FSE
changed the base branch from
feat/926-bots-slots-queue-speed
to
main
September 24, 2026 16:55
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
2 participants
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.
Item 6 of #926 - AutoGet's list expiry, plus a "seen" mark. Stacked on #932 (same changelog heads); retarget to
mainonce that merges.Refresh by age, only where there is no other evidence. With
AUTO_REFETCH_LISTSon, a held list was refreshed only when its bot's advert showed a different date or file count. A bot whose advert shows no date is freshness "unknown" and was never refreshed at all. Such a list is now due once it isUNKNOWN_LIST_MAX_AGE_DAYS(14) old - the interval, per-run cap and "we already asked" mark still apply. A dated bot whose list has not changed is still never refreshed on age. The console line says which reason it was ("X's list is over 14 days old" rather than "has changed")."New" badge. Every fetch stores
seen_at: 0; opening the list in the List Browser callslist_fetch.mark_seen(), which stamps and saves it. The sidebar row carriesunseenand shows a small New badge (en/es/fr). A refreshed list is new again; entries from before this have noseen_atand are never marked.Docs: both changelogs, the setting's help, the
defaults.pycomment andsettings.conf.sample(regenerated).Tests:
tests/test_an_old_list_is_refreshed_and_a_new_one_is_marked.py(10).test_list_freshness's unknown is not changed now holds a 3-day-old list, which is the case it was about. Mutation-checked (no expiry / expiring dated lists / wrong reason / never seen / legacy marked each fail a test). Full suite green on this branch, and also on it merged with #925, #929 and #930.🤖 Generated with Claude Code
https://claude.ai/code/session_01AP6LSxkr4n9dMFNSNMogmW