Systemcore Random Reboots
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- java
- Domain
- embedded-iot
Research direction
Start by reviewing the Driverstation logs and the Systemcore behavior described in the report, comparing alpha7 with the earlier alpha5 symptoms. The issue does not name source files or tests, so first identify the relevant reboot and power-management entry points in the repository. Done means reproducing or isolating the unexpected reboot and documenting a confirmed cause or fix.
Written by the indexing model from the issue text.
Description
Our Systemcore randomly reboots, when the robot is either enabled or disabled. The only message we see in our Driverstation logs is “Disabled due to RobotRequest”. The power LED remains on but the other lights turns off until the reboot completes.
We are currently on alpha7, but we also had a similar issue when we were on alpha5. On alpha5, instead of rebooting, our Systemcore would completely turn off and would need a power cycle to turn back on.
- Dominant language
- Java
- Stars
- 190
- Forks
- 25
- Avg merge
- 6h 28m
- Merged PRs (30d)
- 12
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
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
wpilibsuite/SystemcoreTesting#380 ·
Maintainers usually reply within 1 day
-
Limelight Pending
Difficulty 1/5 Under an hour Newbie friendliness 78/100
wpilibsuite/SystemcoreTesting#315 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
wpilibsuite/SystemcoreTesting#417 · 12 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
wpilibsuite/SystemcoreTesting#416 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
wpilibsuite/SystemcoreTesting#414 ·
Maintainers usually reply within 1 day
All issues in wpilibsuite/SystemcoreTesting
Similar issues
-
backend
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bcgov/nr-forest-client#2524 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
team:Lumberjack
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
OpenLiberty/open-liberty#35998 ·
Maintainers usually reply within 1 day
-
[BUG] SQS SendMessageBatch accepts more than 10 entries instead of TooManyEntriesInBatchRequestPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
floci-io/floci#5319 · 1 comment ·
Maintainers usually reply within 1 day