workbenchdev / workbenchdev/Workbench
The second Rust session always fails
Open
Nobody has claimed this yet.
bug
rust
- Dominant language
- JavaScript
- Stars
- 844
- Forks
- 91
- Avg merge
- 7h 12m
- Merged PRs (30d)
- 1
Description
Steps to reproduce
flatpak kill re.sonny.Workbench.Develrm -rf ~/.var/app/re.sonny.Workbench.Devel- Start Workbench from main
- Open any Rust demo
- Press "Run" - it compiles and execute all good
- Open any other Rust demo
- Press "Run" - it fails with the following
thread '<unnamed>' panicked at code.rs:4:89:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
It appears that running only works after a fresh cargo build?
Contributor guide
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
Reproduce by running Workbench from main, opening one Rust demo, then a second, following the listed Flatpak cleanup steps and observing the panic in code.rs. Compare the first and second runs and trace the session state involved; done means successive Rust demos run without the reported unwrap panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100