feat(herdr-usage): refresh countdown row, stale cache retention, SIGUSR1 refresh#26
Merged
Conversation
…SR1 refresh The section's first row is now a breathing-room spacer carrying a right-aligned status cluster: a next-fetch countdown (with optional --refresh-hint keybind label) that flips to an amber 'cached <age> ago' when a fetch degrades. Fetch and render are split so a minute tick re-renders reset countdowns from the cached snapshot without broker traffic; an errorful sweep retains the previous snapshot instead of shrinking or blanking the section. SIGUSR1 pulls the next fetch forward through the same event loop, so manual refreshes can never overlap a scheduled cycle. Usage rows now cap at 23, reserving the status slot.
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.
The section's first row is now a breathing-room spacer carrying a
right-aligned status cluster: a next-fetch countdown (with optional
--refresh-hint keybind label) that flips to an amber 'cached ago'
when a fetch degrades. Fetch and render are split so a minute tick
re-renders reset countdowns from the cached snapshot without broker
traffic; an errorful sweep retains the previous snapshot instead of
shrinking or blanking the section. SIGUSR1 pulls the next fetch forward
through the same event loop, so manual refreshes can never overlap a
scheduled cycle. Usage rows now cap at 23, reserving the status slot.