This was on Pharo's #offtopic Discord channel, where I assume David Lewis
would not see it…

> lukego - Yesterday at 8:49 AM
> I'm not sure how to report a bug on CommandShell so I will just write this
> here so that it is 
> somewhere:
> PipeJunction>>outputAndError is broken because it attempts to first
> completely read stdout 
> and then to completely read stderr. These streams should actually be read
> in parallel. 
> Otherwise you have a deadlock when a subprocess fills up its stderr
> because it will become 
> blocked on a write(2,...) system call hoping for Pharo to drain the buffer
> and make space on 
> stderr but that never happens because Pharo is only polling stdout.
> I'm working around this with 2>&1 i.e. making sure that only stdout is
> used and never stderr.

I don't think the OP is subscribed to this list, but I'm happy to pass
responses back and forth.



-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Squeak-Dev-f45488.html