WPILib: Debug will result in a non-booting robot program until a regular deploy
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- embedded-iot, operating-systems
Research direction
Start with the debug command and the robotCommand.args replacement described in the issue, then compare that flow with the separate robotCommandDebug script used on the roboRIO. Reproduce the debug, Systemcore reboot, and Driver Station "No code" sequence; done means a debug session still works while a rebooted robot program boots normally without requiring a regular deploy.
Written by the indexing model from the issue text.
Description
Reproduction:
- Debug a Java program "WPILib: Debug a Robot Program"
- Reboot the Systemcore
- The FIRST Driver Station always results as "No code"
This is likely due to the debug command replacing robotCommand.args with the debug server start, which requires an incoming debug connection before allowing to continue. The roboRIO solved this by having a separate robotCommandDebug script that was manually executed for debug, but boot would always use the regular robotCommand script.
- Dominant language
- Java
- Stars
- 188
- Forks
- 24
- Avg merge
- 8h 27m
- Merged PRs (30d)
- 9
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 wpilibsuite/SystemcoreTesting
-
Limelight Pending
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
wpilibsuite/SystemcoreTesting#383 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
wpilibsuite/SystemcoreTesting#380 ·
-
Limelight Pending
Difficulty 1/5 Under an hour Newbie friendliness 78/100
wpilibsuite/SystemcoreTesting#315 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
wpilibsuite/SystemcoreTesting#393 ·
-
Limelight
Difficulty 3/5 1-2 days Newbie friendliness 57/100
wpilibsuite/SystemcoreTesting#389 · 1 comment ·
All issues in wpilibsuite/SystemcoreTesting
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oracle/javavscode#652 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenAPITools/openapi-generator#25014 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
AloisSeckar/demos-java#380 ·