MozillaSecurity / MozillaSecurity/ffpuppet
Output FFPuppet logs to unique file
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 33
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
At the moment FFP logs get included in the browsers stderr log file.
Contributor guide
No contributing guide indexed for this repository
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
The issue does not name a source file, test, or entry point. Start by tracing how FFPuppet launches Firefox and captures browser stderr, then identify where FFP logs are added to that stream. Done means FFP logs are written to a distinct, uniquely named file instead of the browser stderr log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100