Close response file when it is no longer needed.#316
Merged
Conversation
Collaborator
|
Thanks for taking ownership and fixing that fast 👍 |
Closed
|
Hope 3.3.0 is released soon? |
Contributor
Author
|
Yes. We don't have an exact date, but the release is around the corner. Most likely this month. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📄 Context
There is an open issue. #311
📝 Changes
File resource containing response is now closed after Chucker reads from it.
🚫 Breaking
No.
🛠️ How to test
Apply
StrictMode.setVmPolicy(StrictMode.VmPolicy.Builder().detectAll().penaltyLog().build())to the test application. It should no longer warn about opened resources.⏱️ Next steps
Closes #311