Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Unused datasets cleanup counts solution datasets and deletes their solutions

Open
#2,645 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@ihsaan-ullah is already working on this.

Since Oct 9, 2026.

  • #2646 by @ihsaan-ullah — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
django, python
Domain
backend

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
  1. Create a competition from this bundle: Solution-Test-Bundle.zip
  2. Open Resources → Quota and cleanup.
  3. "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

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 codalab/codabench

All issues in codalab/codabench

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.