Make search index freshness dates reflect successful indexing
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Read the requirements in this issue and the related discussions in #675 and #676 first. The issue names History, System > Indexes, NEST indexing stats, and Bonsai and Elastic Cloud, but does not identify source files or tests. Start by locating the date displays and indexing paths; done means agreed semantics are implemented with tests for success, failure, partial success, unknown state, backend selection, and timezone handling.
Written by the indexing model from the issue text.
Description
Problem
The modified/current-as-of dates in History and System > Indexes do not establish when the displayed search data was successfully indexed.
- All three History pages display
DateTime.UtcNow.ToPacificTime().AddMinutes(-5).ToLocalTime(). This advances with the request clock even if indexing has stopped or failed. - System > Indexes converts NEST
IndexingStats.TimetoDateTime. This property reads theindex_timestring, a cumulative indexing duration rather than a timestamp. The default stats request omits the human-readable field, so the string is null andConvert.ToDateTime(null)returnsDateTime.MinValue. When a duration string such as1sis present, the conversion throwsFormatException.
PR #676 intentionally restores the existing date displays, formatting, tooltips, and data behavior at the user's request. The dual-backend work in #675 should not remove this useful UI while its accuracy requirements are unresolved. This issue tracks the accuracy work separately.
Requirements to define
- Decide what each displayed date means, including the difference between a successful indexing operation and a guarantee that all relevant source changes are searchable.
- Report dates for the configured read backend and relevant index. Bonsai and Elastic Cloud may have different successful work and failures during dual indexing.
- Define how failed operations, partial success across batches/indexes/targets, and full-index replacement affect the displayed value. An attempted or partly successful job must not imply that every result is current.
- Define the unknown or unavailable state and consistent timezone conversion, formatting, and tooltip wording.
- Preserve a useful date display for users, with tests covering success, failure, partial success, unknown state, backend selection, and timezone handling.
Choose the source and storage of these dates after the requirements are agreed. This issue does not prescribe SQL tracking, durable recovery, retry queues, or cross-process coordination, and does not expand the scope of #675.
Related: #675 and #676.
- Dominant language
- C#
- Stars
- 7
- Forks
- 5
- Avg merge
- 9h 3m
- Merged PRs (30d)
- 5
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ucdavis/Purchasing
-
remove elmahOpen
Difficulty 1/5 Under an hour Newbie friendliness 68/100
ucdavis/Purchasing#436 ·
-
Refactor configsPossibly taken @jSylvestre claimed this 10 days ago. Open
ucdavis/Purchasing#683 · 1 assignee ·
-
Add local resumable search backfill and verification runnerPossibly taken @srkirkland claimed this 24 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
ucdavis/Purchasing#678 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
ucdavis/Purchasing#668 ·
-
AE API field length issueMay be free again @jSylvestre claimed this 39 days ago, and no pull request is open. Open
ucdavis/Purchasing#665 · 1 assignee ·
All issues in ucdavis/Purchasing
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Bug IronPython Python 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyrevitlabs/pyRevit#4184 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
yusei36/KeePassPasskey#66 · 2 comments ·
Maintainers usually reply within 1 day
-
🐛 bug 🕒 low effort good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
guibranco/Sankhya-SDK-dotnet#654 ·
Maintainers usually reply within 1 day
-
巫女のセリフに声を付けるOpenassets claude-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Fialuxe/MouthOfGod_System#358 ·
Maintainers usually reply within 1 day