`byteStringOutput` breaks `withProcessTerm`

[SmartHypercube]

1. byteStringOutput blocks and waits for the entire output in ssCreate.
2. startProcess calls ssCreate.
3. So startProcess blocks if I use byteStringOutput. (Well, this is already bad.)
4. withProcessTerm is broken because it blocks in the startProcess stage. The user-provided action can only run after stdout is closed.

This bug makes this library unsuitable for almost all my use cases :( Since I often need to capture the output while setting some kind of timeout on the subprocess. Sadly I'm not sure how it can be fixed without a major redesign.

(Sorry if this is a duplicate of other open issues. I checked them but I'm not sure.)

[sol]

@SmartHypercube can you give exact steps on how to reproduce this?

[SmartHypercube]

#!/usr/bin/env stack
-- stack script --resolver lts-22.33 --package typed-process
import Control.Concurrent
import System.Process.Typed

main :: IO ()
main = do
    withProcessTerm (setStdout byteStringOutput $ proc "sleep" ["10"]) $ \_ -> do
        print 1
        threadDelay 5_000_000
        print 2

Expected behavior: sleep is killed after 5 seconds.
Actual behavior: The program runs for 10 seconds.