-
Notifications
You must be signed in to change notification settings - Fork 92
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
Connection is leaking #65
Comments
Adding the logs: 2021-06-16 12:05:44.822 WARN 14179 --- [ ConnectionPool] c.s.g.shade.okhttp3.OkHttpClient : A connection to https://github.corp.com/ was leaked. Did you forget to close a response body? java.lang.Throwable: response.body().close() |
This fixes several warnings of this form (spotify#65): A connection to https://github.com/ was leaked. Did you forget to close a response body? According to the okhttp documentation: "Response bodies must be closed and may be consumed only once" https://square.github.io/okhttp/4.x/okhttp/okhttp3/-response/body/
This fixes several warnings of this form (#65): A connection to https://github.com/ was leaked. Did you forget to close a response body? According to the okhttp documentation: "Response bodies must be closed and may be consumed only once" https://square.github.io/okhttp/4.x/okhttp/okhttp3/-response/body/
I think #70 closes this; I have added this to my app and at this point i havent seen any issues. |
Closing this issue since it seems to be fixed. Additionally, from 0.4.x onwards, you can use your own HTTP client so you can customise this behaviour however you want. |
I notice the error logs "A connection to http url was leaked when am using the library. Did you forget to close a response body?" is something am seeing while using the library. I don't see any close methods on the client and response is ignored while making API call to repoClient.setCommitStatus(). How is the library letting its users to close the http connections ?
The text was updated successfully, but these errors were encountered: