Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve handling of bulk build reports #5

Open
bsiegert opened this issue Mar 29, 2015 · 1 comment
Open

Improve handling of bulk build reports #5

bsiegert opened this issue Mar 29, 2015 · 1 comment
Assignees
@bsiegert

Comments

@bsiegert
Copy link
Owner

The red error bar saying "try recreating the index" is a pretty bad UI.

  • store the last fetch error in the database and surface it
  • use a custom queue to increase the time between fetches
  • for extra points: make the reindex show the status interactively.
@bsiegert bsiegert self-assigned this Mar 29, 2015
bsiegert added a commit that referenced this issue Nov 10, 2015
@bsiegert
Introduce a new ingest.Status type.
729706e 
This holds the status of a report ingestion. It is updated at each
step of FetchReport and deleted when the ingestion is done.
Simultaneously, the entry is written to memcache.

There is no code to return the status yet, and the UI has no hooks
for that.

Update #5.
@bsiegert bsiegert mentioned this issue Jun 22, 2024
Closed
@bsiegert
Copy link
Owner Author

Design sketch:

  • JSON endpoint for calling ingest.FetchReport, which runs in the foreground instead of in the background as before.
  • Detect 0 results in the build status page and offer a button for triggering a re-index
  • When clicked, XHR request, wait for it to come back, then show the status directly on the same page.

bsiegert added a commit that referenced this issue Jul 16, 2024
@bsiegert
Store the last error when fetching details.
7e6cfbf 
When fetching the detailed bulk build report and there is an error,
store the error in the database and surface it on the build page.

There is more to be done here (including a better UI) but this at least
shows that there has been a problem.

Update #5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bsiegert bsiegert

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bsiegert