Show current harvest progress separately from last success - #22
Merged
Merged
Conversation
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.
A running repository harvest inherited the previous run's completion timestamp, so USGS appeared to be running since yesterday. The dashboard now separates Last Successful Harvest from Latest Harvest, showing the latest run's start time and a readable current stage (fetching metadata, importing records, updating the search index, refreshing thumbnails, or saving harvest files).
Derive the last successful completion from successful harvest history. Keep a running run's completion timestamp null; later failed runs do not replace the last successful harvest. Unknown stages display “Processing,” and repositories without successful history say so explicitly. The repository JSON also exposes
last_run_stageandlast_successful_harvest_at.Validation: 23 focused tests passed, including PostgreSQL integration checks for running and failed runs after a successful harvest, every stage label, and missing history. Ruff and diff checks pass.
No deployment included; ready for merge and a patch release.