-
Notifications
You must be signed in to change notification settings - Fork 928
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sbt --client "java.io.IOException: Stream Closed" exception for Play app #6515
Comments
@dkovalenko Thanks for the report. Could you tell us which version of sbt and Play you're using? If I remember correctly, there was an issue in sbt's input handling as well because JLine does its own input reading instead of the assigned |
Yeah, play is using a FileInputStream for some reason. That will definitely not work with client mode: https://github.com/playframework/playframework/blob/53e55f017f508f0dcdf2a70327bd73153fe87e5e/dev-mode/sbt-plugin/src/main/scala/play/sbt/PlayInteractionMode.scala#L84-L87. This should probably be a play issue. They shouldn't need to create a non blocking input stream reader because sbt makes System.in non-blocking starting with 1.4.0. |
Sbt version: 1.5.2 |
Can we somehow create an issue for the play framework maintainers to fix that? I can do that but I lack some technical details and don't want to be a secondhand source. |
@dkovalenko here you go - playframework/playframework#10864 |
@eed3si9n You can close this issue here, I am taking care of it in the Play repo: playframework/playframework#11061 |
Sounds good |
steps
problem
After this sbt server continues to run play application, but I can't see any output from it and can't stop it other than killing parent sbt process.
expectation
Play server is running properly in sbt --client mode, I can see the output of the server in my console, I can stop the application with Ctrl+C.
notes
Sbt version: 1.5.2
Play framework version: 2.7.9
The text was updated successfully, but these errors were encountered: