editor/view: errors in the view go routine should be reported on close.
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- Go
- Stars
- 60
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
The view go routine can generate errors in a couple of places. Currently, these are just ignored and the go routine exits. They should be tracked and returned by Close.
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 locating the view goroutine and its Close method, then inspect the couple of places where the goroutine can generate errors. Track those errors through shutdown so Close returns them, and verify that errors are no longer silently ignored when the goroutine exits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100