Handle NewPane panic
Open
Nobody has claimed this yet.
bug
good first issue
hacktoberfest
- Dominant language
- Go
- Stars
- 38
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Line ./peers/pane.go:101 crash very rarely, but it does happen.
It will probably be more common on slow hosts and the problem happens
when the split a pane twice in a row. The first split will work, but the
second could crash if the first one's shell hasn't finished starting up.
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 peers/pane.go:101 and trace the NewPane path involved when two pane splits happen before the first shell finishes starting, especially on a slow host. Reproduce the rapid split scenario and verify that the second split no longer panics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100