Model training scripts dump generated artifacts directly into the repo root
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- machine-learning, tooling
Research direction
Start by inspecting the model-training scripts under scripts/ and the generated artifact names listed in the issue. Trace which entry points write into the repository root, then determine a project-consistent output location and verify training no longer places generated files there.
Written by the indexing model from the issue text.
Description
Problem
The repo root accumulates a large number of generated artifacts — mostly from model training — that are correctly .gitignore'd but still physically clutter the directory, making the project structure hard to navigate in file explorers, ls, and IDEs. The exact number depends on how many models have been trained locally during experimentation.
For example, after training several models, the root can contain ~59 items on disk while only ~31 are tracked source files — the rest are generated artifacts. Actual project files get buried among generated directories:
$ ls
CITATION.cff fenixcomponentmodel/ regressormodel_data_X.zst.etag
CODE_OF_CONDUCT.md functions/ regressormodel_data_y
CONTRIBUTING.md http_service/ regressormodel_data_y.zst
LICENSE indexdir/ regressormodel_data_y.zst.etag
MANIFEST.in infra/ releasenotemodel/
README.md mcp/ requirements.txt
VERSION metrics.json scripts/
__pycache__/ node_modules/ setup.py
annotateignoremodel/ notebooks/ spambugmodel/
backoutmodel/ patches/ stepstoreproducemodel/
bugbug/ pyproject.toml test-requirements.txt
bugbug.egg-info/ regressionmodel.zst testfailuremodel
bugtypemodel/ regressormodel.zst testgroupselectmodel/
cache/ regressormodel.zst.etag testlabelselectmodel/
componentmodel/ regressormodel_data_X tests/
crashcomponentmodel/ regressormodel_data_X.zst ui/
data/ regressormodel_data_X.zst… upliftmodel/
...
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
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.
More from mozilla/bugbug
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
good-first-bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
zostera/django-bootstrap4#894 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3276 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
zilliztech/memsearch#759 ·