clearlydefined / clearlydefined/service

The UX is unclear about when manually requested harvest operations will complete

Open
#1,081 0 comments 3 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
51
Forks
46
PR merge metrics
No merged PRs in 30d

Description

I'm trying to register a specific commit of the Tree-Sitter repo in use in a project. I submitted the following to https://clearlydefined.io/harvest

![Image](https://github.com/clearlydefined/service/assets/5387680/a5fefc85-ff0f-4e4a-9b78-f58246fdc52d)

A popup appears indicating that something has started...

![Image](https://github.com/clearlydefined/service/assets/5387680/8da1377d-8e3c-4517-9725-ec0cdffb7693)

But it's unclear what that means in terms of timing.

- Is Harvest starting immediately or is it in some background queue that will eventually be processed?
- What is the ETA for the operation's completion?
- Do I need to stay on this page to ensure the operation completes?
- Can I expect to get a notification on this page when the operation completes?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.