summaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
authorJoey Hess2020-06-10 15:19:02 -0400
committerJoey Hess2020-06-10 15:19:02 -0400
commitad2c6ae1f904b5d94e227944c96db657410934ee (patch)
treeb2cdc799c866197a9a4dd9cd70e07c3bc83d40bd /doc/todo
parenta077594770132b4a07b168936d07385ff0c618d6 (diff)
meh
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/depend_on_concurrent-output.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/todo/depend_on_concurrent-output.mdwn b/doc/todo/depend_on_concurrent-output.mdwn
index c3641385..2503fe2e 100644
--- a/doc/todo/depend_on_concurrent-output.mdwn
+++ b/doc/todo/depend_on_concurrent-output.mdwn
@@ -27,3 +27,16 @@ Waiting on concurrent-output reaching Debian stable.
> from debian. That is a somewhat old version and perhaps it was buggy?
> However, I have not had any luck reproducing the problem there running
> readProcess in ghci. --[[Joey]]
+>
+> > Tried again in 2020, same bugs still happened. On a system running
+> > debian unstable with concurrent-output 1.10.9, and a system running stable that
+> > had cabal installed concurrent-output 1.10.11.
+> >
+> > The former system (kite) had the strange output problem.
+> >
+> > The latter system (keysafe) seemed ok but crashed at the end with
+> > a STM transaction deadlock. Downgrading to concurrent-output 1.10.6
+> > eliminated that problem.
+> >
+> > This is really looking like a reversion, or several, in newer
+> > versions of concurrent-output. --[[Joey]]