Add more information in the rule page
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 36
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 7
Description
Description
I would love to have more information about rules such as:
- If they are stuck, what is the error? (e.g.
RequestErrMsg.NO_SOURCES:RequestState.NO_SOURCES). This could be just a mouse over box when hovering over thestuckelement. - When was it stuck? (
stuck_at) - Time should have minutes / second precision too, just like in the CLI. At least you should be able to get this somehow (hovering over them?)
Motivation
No response
Change
No response
Additional Information
- The Rucio API needs to be changed.
Contributor guide
No contributing guide indexed for this repository
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 at the rule page and inspect how stuck status and rule times are currently displayed, then compare the available precision with the CLI. Done means showing the stuck error and stuck_at value, and providing minute/second precision through the page or hover text; check whether the Rucio API must change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100