robotpy / robotpy/robotpy-installer
deploy: Import robot code in subprocess so we can suppress things like phoenix
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 18
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
the ctre stderr is really obnoxious during deploy, we should start the robot class in a subprocess so that we can suppress the output if it succeeds.
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
Inspect the deploy flow where the robot class is imported and identify how deployment currently captures or displays CTRE stderr. Verify how subprocess failures are surfaced. Done means successful deploys suppress the unwanted output while failures remain visible and actionable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100