diff options
| author | Joey Hess <joeyh@joeyh.name> | 2016-03-06 13:57:50 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-03-06 13:57:50 -0400 |
| commit | 82d0473dd00401004fe996a6a1349d976fe979a7 (patch) | |
| tree | 5b92d55aa05b32d1fc21429490493e910bf362b9 | |
| parent | 3db71c4f83da6a20c040a44e4fe0cf64c5303190 (diff) | |
comment
| -rw-r--r-- | doc/forum/Weird_SSH_issue/comment_3_8347b69df64b737f4e5df854c55d4e92._comment | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/forum/Weird_SSH_issue/comment_3_8347b69df64b737f4e5df854c55d4e92._comment b/doc/forum/Weird_SSH_issue/comment_3_8347b69df64b737f4e5df854c55d4e92._comment new file mode 100644 index 00000000..adc64e5d --- /dev/null +++ b/doc/forum/Weird_SSH_issue/comment_3_8347b69df64b737f4e5df854c55d4e92._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2016-03-06T17:54:20Z" + content=""" +It also seemed to affect the first spin and not the second one when I was +seeing it. But that was 1-2 weeks ago, and I am not currently reproducing +the issue. + +If you can reproduce it consistently, it would be good to check if the +concurrent output layer, which involves intercepting all command output and +serializing it, might be involved. If you edit +`src/Utility/Process/Shim.hs` and make it simply `import System.Process as X` +and remove the other import, that will bypass the concurrent output layer. +"""]] |