Repository navigation
fix(web): hide collection status until the first round after restart - #12
Merged
Merged
Conversation
The zero time (0001-01-01) is truthy, so the status line showed a placeholder last-reclaim time; use the shared validTime check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Background
Before the first collection round after a restart, the status times are Go zero values (0001-01-01). The status page tested them for truthiness, so it showed a placeholder last-reclaim time.
Changes
The collection status line in
operations-page.jsuses the sharedA.validTimecheck forlast_run_atandlast_reclaim_at. It stays hidden until the first round and omits the last-reclaim part when nothing has been reclaimed.Risks
Display only.
Testing
node scripts/check-web.mjspasses.🤖 Generated with Claude Code