matthewmueller / matthewmueller/dev
Watcher sometimes dies
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
github.com/matthewmueller/dev/internal/cli.(*CLI).Watch.func1({0x1400007c300?, 0x100c75200?, 0x1400024df00?})
/Users/m/dev/src/github.com/matthewmueller/dev/internal/cli/watch.go:64 +0x1f4
github.com/livebud/watcher.Watch.func1.1()
/Users/m/dev/pkg/mod/github.com/livebud/watcher@v0.0.3/watcher.go:126 +0x3c
created by time.goFunc
/usr/local/go/src/time/sleep.go:215 +0x38
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 reading internal/cli/watch.go at line 64, then compare the call path with github.com/livebud/watcher@v0.0.3/watcher.go at line 126. Reproduce the watcher failure if possible and determine the condition that causes it to die. Done means the watcher no longer exits unexpectedly and the behavior is covered by an appropriate regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100