Phoenix logging crashing robot code with USB file system errors
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
The crash is an uncaught std::filesystem_error thrown while reading the size of a .hoot log file on a failing USB drive, so start in the Phoenix logging code that calls file size on the log path. Reproducing it needs a log file on a faulty or simulated I/O-error filesystem, and the fix should make the logger handle the error without terminating the robot code. The issue does not say what the expected behavior should be, so confirm that with maintainers first.
Written by the indexing model from the issue text.
Description
I was helping a team that had a usb drive with filesystem errors, and it looks like at least once phoenix crashed the robot code.
Oct 30 17:24:28 robot bash[881]: terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
Oct 30 17:24:28 robot bash[881]: what(): filesystem error: cannot get file size: Input/output error [/u/logs/2026-04-29_22-02-57/rio_2026-04-29_22-03-04.hoot]
- Dominant language
- Java
- Stars
- 195
- Forks
- 26
- Avg merge
- 11h 58m
- Merged PRs (30d)
- 10
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 2/5 1-3 hours Newbie friendliness 65/100
wpilibsuite/SystemcoreTesting#449 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
wpilibsuite/SystemcoreTesting#446 · 1 comment ·
Maintainers usually reply within 1 day
-
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
-
SparkMax Missing Status Frame 8Possibly taken @jfabellera claimed this 2 days ago. OpenPending REV Robotics
wpilibsuite/SystemcoreTesting#448 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in wpilibsuite/SystemcoreTesting
Similar issues
-
bug emitter:client:csharp
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/typespec#12572 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
[BUG]: Java SDK MountRequest always sends update-optional fields, resetting stored mount settingsOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
GCC 15.2: -Wcast-qual warning - cast discards const qualifier from pointer target type (H5trace.c)Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
[Bug] RemotingHelper.connect swaps the socket send and receive buffer configurationPossibly taken @amalsaidov claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
needs-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days