Log the run command used to launch each step by default
Open
Nobody has claimed this yet.
enhancement
Good First Issue
- Dominant language
- Python
- Stars
- 161
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
Maestro currently logs the run command it issues for each step to ``DEBUG``; however, this would be useful information for Maestro to always log in the output for debugging and provenance. For larger studies, it's not always reasonable to rerun the study to generate the debug logs.
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.
Research direction
Start by tracing where Maestro currently emits each step's run command at DEBUG and identify the corresponding normal-output path. Done means each step's command is included by default in the output while remaining useful for debugging and provenance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100