Add a "No FTS submission in the last X days" message

Open Beginner friendly
#769 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend

Research direction

Start in the rule/page/<rule_id> page under Locks and locate the toast shown when generating the FTS link for a STUCK rule. Update the toast to indicate that no FTS submission occurred in the last X days, then verify the message appears instead of the current error.

Written by the indexing model from the issue text.

Description

enhancement
Description

Add an indication to let the users know when the last FTS submission was done, e.g. "Rule has no FTS submissions in the last X days".

Motivation

The “Generate (FTS) link” button in the rule/page/<rule_id> page under Locks returns an error for STUCK rules (see screenshot). This is likely due to the request no longer being present in the REQUESTS table, as it has been moved to REQUESTS_HISTORY.

In this case for example, instead of showing an error, the UI could inform the user that there have been no FTS submissions in the last X days, where X is greater than the time required for a request to be moved to the history table.

Image
Change

Update the toast text

Additional Information
  • The Rucio API needs to be changed.
Dominant language
TypeScript
Stars
5
Forks
36
Avg merge
6d 17h
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rucio/webui

All issues in rucio/webui

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.