JakeWharton / JakeWharton/finalization-hook
Figure out the appropriate list of signals, why SIGPIPE wasn't included
Open
enhancement
- Dominant language
- Kotlin
- Stars
- 76
- Forks
- 0
- Avg merge
- 19h 40m
- Merged PRs (30d)
- 13
Description
User getting a SIGPIPE and not seeing the hook trigger. Why did we leave that (and other signals) out?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating the signal-handling entry point and current signal list, then compare SIGPIPE with the other omitted signals; done means determining and documenting the appropriate list and addressing the reported SIGPIPE behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100