thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 234
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
Got this error when showing the logs via sonic-pi-tool logs:
[Run 7, Time 497.6501]
├ cue :drum
└ sync :lead
=> Starting run 35
=> Thread :live_loop_drum exists: skipping creation
=> Thread :live_loop_lead exists: skipping creation
=> Thread :live_loop_bass exists: skipping creation
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value
: ReadError(Error { repr: Custom(Custom { kind: UnexpectedEof, error:
StringError("failed to fill whole buffer") }) })', src/libcore/result.
rs:868
note: Run with `RUST_BACKTRACE=1` for a backtrace.
Just leaving it here for now, but I can try to get more details later if needed (a backtrace for example).
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
Start by reproducing the failure with sonic-pi-tool logs and capture the requested backtrace. Trace the log-reading path from that command to the reported UnexpectedEof and determine the relevant error-handling entry point. Done means the command no longer panics on this input and has regression coverage for the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100