Unused datasets cleanup counts solution datasets and deletes their solutions
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
The unused-dataset counter and the delete button share one query, so the fix starts there in the Resources quota and cleanup code. Check how solution datasets are linked to solutions and whether the query excludes them. Pull request #2646 is already open against this issue, so confirm its status before starting work. Done means the counter and the delete action both skip solution datasets.
Written by the indexing model from the issue text.
Description
On the Resources page, the quota cleanup counts solution datasets under "Unused Datasets and Programs", even when a solution that's linked to a task is using them.
The counter only treats a dataset as used if a task uses it. Solutions point to their dataset in a different way, so a solution dataset always looks unused.
The "Delete unused datasets/programs" button uses the same query, so clicking it would delete those solution datasets, and the solutions using them would be deleted along with them.
Steps to reproduce
- Create a competition from this bundle: Solution-Test-Bundle.zip
- Open Resources → Quota and cleanup.
- "Unused Datasets and Programs" includes the solution's dataset.
Proposed:
because the use of solution is not very clear for now, we will remove it from the deletion so that we don't do any unintended delete. Later on when the use of solution becomes clear, we can carefully design how to delete unused solutions.
- Dominant language
- Python
- Stars
- 183
- Forks
- 80
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 32
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from codalab/codabench
-
Wrong count for failed submissions in Resource interfacePossibly taken @ihsaan-ullah claimed this 4 days ago. OpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Resource Interface: Improve time formatPossibly taken @ihsaan-ullah claimed this 3 days ago. OpenBeginner Enhancement UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 12/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
codalab/codabench#2651 · 1 comment ·
Maintainers usually reply within 1 day
-
Email redesignOpenEnhancement UI
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
All issues in codalab/codabench
Similar issues
-
bug Triage-Needed
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
FuRongJun-1999/dsh-memory#170 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
521xueweihan/HelloGitHub#3940 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100