R2NorthstarTools / R2NorthstarTools/FlightCore
Catch panics to show error message in frontend
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Panics in async threads are not a super big deal as the main process still stays alive.
However, in cases like file download where we currently show no progress indicator they don't clear the state in frontend and as such it will still say "downloading" giving the user the wrong impression that a download is still happening.
(ofc download progress indicator should also still be addressed)
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 at the async file-download operation and the frontend state that displays "downloading"; the payload does not name specific files or tests. Trace what happens when an async thread panics, then verify that the frontend shows an error and clears the downloading state when the operation fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, tauri
- Domain
- backend, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100