Privately notice people when working on stuff that takes a long time
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Example:
<AlexDaniel> coverable6test: HEAD
say ‘hi’
<coverable6> AlexDaniel, https://gist.github.com/de39ac3fc8736f45f305a68731617566
During these 30 seconds the user does not know if the bot is doing something or not. Maybe the bot is not online? Or maybe it failed during the process? If everything is ok, then how long would the user need to wait?
It should probably drop a private message if the query is expected to take a long time. This message should include the approximate time to wait. Also, it should not send this message too often (e.g. once an hour max).
Contributor 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.
Research direction
No file or test is named in the issue. Start by locating the bot's query handling and private-message entry points, then trace how long-running work is detected. Done means long queries privately report an approximate wait without sending that notice more than once per hour.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100