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
Error while closing input stream from client #5566
Comments
I got this when stopping Eclipse which includes a Buildship 3.0.1 where I ran a task with the help of the tooling API:
|
The one from Eclipse is slightly different. I just refactored a custom task to use the worker api. I have the daemon currently disabled locally because I have a slight RAM shortage and build many different projects with different Gradle versions, so the daemons killed it finally. Now my build also started to show this error and quite regular, after the build already finished successfully:
I tracked it down a bit. As far as I understood the code, Now in Gradle we have the The But this is most probably a threading issue. One way to work-around the problem (from what I have seen, but as the problem is intermittent, not sure) is to set Another work-around (from what I have seen so far) is to set the A correct fix might maybe be to do the |
Ah, wait, that makes no sense, the workaround is only about input stream and what is stacked are output streams, so I think I prefer the |
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution. |
I see this in gradle 7.1.1 and in 7.2 every time we "./gradlew build" from root of https://github.com/deanhiller/webpieces It is not impacting the build BUT developers keep looking into it thinking that is what broke the build :( as they do not know it is a red herring. |
We have a gradle task that dispatches jobs to jenkins and we wait for the jenkins build to complete before moving on to the next task, and we get a very similar issue. Here is the stacktrace:
We are using gradle 7.5.1. |
Still happens in Gradle 8.1.1. |
Just got this while running
gradle sanityCheck
on our own repo, but could not reproduce it.The text was updated successfully, but these errors were encountered: