output is not streamed when used with sbtn

[joprice]

When using revolver with sbtn, I see no output from the forked task. I assume the output is being streamed on the server side and is not ending up in the client's view. Perhaps it needs to be streamed to a particular log to allow that to work as expected with sbtn?

[atraastrum]

I'm experiencing similar issue with sbtn. When the code is recompiled and application is restarted output doesn't longer appear in the sbt shell. Which kind of defeats the purpose of ~reStart since you have to stop application and run it again.

At least with ~reStart you can see output until you recompile.

With reStart the output is not streamed.

[arturaz]

I poked around this and I believe it's an issue with SBT itself, not the plugin.

Quote from Discord:

@eed3si9n I have reason to believe that when SBT re-runs a command in watch mode the stdout/stderr streams somehow get detached from a forked process.

Specifically I'm looking into the #99. The plugin doesn't seem to be doing much, it just uses the Fork.java.fork API to launch a process in the background. However, after SBT restarts the task after the file change the stdout isn't seen anymore.

I've tried using StdoutOutput, BufferedOutput and LoggedOutput strategies, they all act the same.

I have a suspicion that somehow when the task is restarted the output goes to some old output stream which makes it invisible and it's a problem in SBT itself, not sbt-revolver.

Do you have any ideas where I could start debugging this?