Imported From: https://issues.scala-lang.org/browse/SI-7963?orig=1
Reporter: legendre
Affected Versions: 2.10.2, 2.11.0-M4, 2.11.0-M7, 2.11.0, 2.12.0-M1

legendre said:
Now that #8768 has been fixed, could someone check if this issue is still valid ? I can't test it since there is no release for the 2.12.0-M1 yet.
Thanks.

@som-snytt said:

import scala.sys.process._

object Test extends App {
  "ls".run(true).exitValue()
  val line = io.StdIn.readLine("Foo bar ? ")
  Console println s"[$line]"
}

Foo bar ? bye
Exception in thread "Thread-0" java.io.IOException: Stream closed
	at java.lang.ProcessBuilder$NullOutputStream.write(ProcessBuilder.java:433)
	at java.io.OutputStream.write(OutputStream.java:116)
	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
	at java.io.FilterOutputStream.close(FilterOutputStream.java:158)
	at scala.sys.process.BasicIO$$anonfun$input$1.apply(BasicIO.scala:200)
	at scala.sys.process.BasicIO$$anonfun$input$1.apply(BasicIO.scala:198)
	at scala.sys.process.ProcessBuilderImpl$Simple$$anonfun$2.apply$mcV$sp(ProcessBuilderImpl.scala:73)
	at scala.sys.process.ProcessImpl$Spawn$$anon$1.run(ProcessImpl.scala:23)

[]

legendre said (edited on Mar 6, 2015 5:05:37 PM UTC):
@A. P. Marki => I also have the same exception that comes from nowhere now....

I analyzed the issue in sbt/sbt#3737 (comment). We basically need a port of the fix of this old sbt issue: sbt/sbt#327.

(Not so sure about "good first issue" and "quickfix", though ;)

I remember thinking that upgrading to the Java 7 API could happen after sys.process became a module. Consumers could benefit from a shorter release cycle for the module.

(I do think it's a "good first issue" in the sense that it doesn't involve compiler internals or juggling a lot of competing concerns, it's a focused thing that can be tackled in isolation. There are precious few open issues in scala/bug that are actually easy and quick.)

@SethTisue you need a label for "good GSOC issue."

(I do think it's a "good first issue" in the sense that it doesn't involve compiler internals or juggling a lot of competing concerns, it's a focused thing that can be tackled in isolation. There are precious few open issues in scala/bug that are actually easy and quick.)

Haha, I see, everything is relative I guess.

in 2.13, scala.sys will become its own module, at which point this could be addressed if someone cares to. closing since scala.sys issues will no longer be tracked here in scala/bug. I've made a "module:scala.sys" label so we can find relevant issues once the module has its own repo

I'll tackle on this for OSS Hackathon@ScalaMatsuri 2019, though I'm not sure whether I can finish...