[P1] Create output directories before running local evidence tools
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start with scripts/doctor.py, scripts/capture_demo.py, scripts/evaluate.py, scripts/bootstrap_local.py, and scripts/tune_example.py; trace each output path and when it is opened relative to costly work. Add a small offline check for missing output directories, then verify reports can be written on a clean checkout without manual setup. Done means producers create their own parent directories, recorded attempts are preserved, generated evidence remains ignored, and prerequisite order is documented.
Written by the indexing model from the issue text.
Description
Finding
Reviewed commit: 0549e5b1e6d88aaa46a0e580dcaad5b177446997.
Generated submission/ and artifacts/ directories are intentionally excluded from Git. Several local tools assume those directories already exist, so the documented workflow is not reproducible from a fresh checkout without an undocumented setup step.
Confirmed reproduction
With dependencies installed and neither output directory present:
python scripts/doctor.py
This runs without --live and makes no inference request. It exits 1 at doctor.py:42 with FileNotFoundError while writing submission/environment.json, masking the actual Ollama availability result.
This does not establish a failure in the owner's already prepared local workspace.
Affected producers
doctor.py:41–42: missing parent for the environment report.capture_demo.py:25–27createsartifacts/raw, but lines 105–107 assumesubmission/exists after a potentially expensive capture.evaluate.py:25–26creates raw-result directories, but line 52 assumes the summary directory exists.bootstrap_local.py:49opensartifacts/ollama.logwithout creating its parent, potentially after a large download.tune_example.py:21–22creates a nested directory withoutparents=True.
Requested change and acceptance
- Each producer creates its own output parents before expensive work begins.
- On a clean checkout, the non-live doctor writes a truthful environment report, including
NOT_RUNand any actual availability error. - Capture and evaluation can persist success and failure reports without manual
mkdir. - Bootstrap prepares its log directory before downloading/starting tooling.
- Existing recorded attempts are preserved and generated media/evidence stay ignored by Git.
- Document prerequisites and order for tools that consume earlier outputs, such as capture → render → build sample.
- Verify directory behavior with a small offline check; no model download or live experiment is needed to prove this fix.
Priority: fix before asking another person to reproduce the launch evidence.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 25m
- Merged PRs (30d)
- 5
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 drevendev/PatchPitch
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
drevendev/PatchPitch#74 ·
-
[RFC] Ten optional no-card integrations for the Full Release Kit: pilots, roadmap and exit plansOpendocumentation enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
drevendev/PatchPitch#89 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
drevendev/PatchPitch#88 ·
-
[P1][v0.3.x] Private GitHub URL intake through explicit local read-only auth (no secrets in drafts)Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
drevendev/PatchPitch#87 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
drevendev/PatchPitch#86 ·
All issues in drevendev/PatchPitch
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
MISP/misp-workbench#496 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
fossasia/visdom-dev#69 ·
Maintainers usually reply within 3 days
-
[Bug] Parameters named like a property break to_xcal()Possibly taken @atharvasalunke1267 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
collective/icalendar#2018 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day