Endeavour233

Check the Object from the serviceMethodCache again

4

I wrote a test `annotationParsingFailureObservedByMultipleWaitingThreads()` (modified from @JakeWharton 's `annotationParsingFailureObservedByWaitingThreads`) in `RetrofitTest.java` to mock the situation I mentioned in #4114 . And I found that the code in `base:trunk` branch...

This pr might resolves #4072 partially. - [x] `CHANGELOG.md`'s "Unreleased" section has been updated, if applicable.

fork项目后，README-Algorithm section中利用shield.io生成的用于track刷题数的动态badge仍然是在track原项目的issue数的（预期应该track fork后的项目的issue（即刷题进度））感觉有两种修复思路：  1. 在usage中指导用户手动改一下README文档，把"Doragd/Algorithm"改成自己的用户名和repo名 2. 在main.py中加一个更新badge的脚本，对"Doragd/Algorithm"进行替换 因为我不太会用python和shield.io, 也不太确定哪种修改会更好一点，所以就提一下issue和想法，仅供参考～

Previous doc shows that body is always null for cacheResponse, networkResponse and priorResponse. It's confusing since the body property can't be null. This pull request updates the doc to show...