List processed commands in uptime message
Open
Nobody has claimed this yet.
whateverable
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
<timotimo> hm, the uptime message could include stats on what it's been doing since it was last started
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
Start by locating the code that generates the uptime message. Determine which processed-command statistics are available since startup and define the expected wording and scope with the maintainers. Done means the uptime response includes the agreed statistics and has coverage for the new behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100