Possible deadlock
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 60
- Forks
- 9
- Avg merge
- 3h 59m
- Merged PRs (30d)
- 8
Description
I learned recently if you waitForExit without first draining the standard output and error streams the system can deadlock, because it refuses to allow more data to be streamed out of the child process when its output buffers become full. I don't see any code for handling that situation here.
Here's an example of how it's done.
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 package's process-execution entry point and compare its waitForExit handling with Sources/gyb-swift/ProcessUtilities.swift lines 125-219. Done means the reported deadlock scenario is addressed for child-process standard output and error streams.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100