Changelog
*Sourced from [okhttp's changelog](https://github.com/square/okhttp/blob/master/docs/changelog_3x.md).*
> OkHttp 3.x Change Log
> =====================
>
> ## Version 3.14.4
>
> _2019-09-29_
>
> * Fix: Cancel calls that fail due to unexpected exceptions. We had a bug where an enqueued call
> would never call back if it crashed with an unchecked throwable, such as a
> `NullPointerException` or `OutOfMemoryError`. We now call `Callback.onFailure()` with an
> `IOException` that reports the call as canceled. The triggering exception is still delivered to
> the thread's `UncaughtExceptionHandler`.
> * Fix: Don't evict incomplete entries when iterating the cache. We had a bug where iterating
> `Cache.urls()` would prevent in-flight entries from being written.
>
>
> ## Version 3.14.3
>
> _2019-09-10_
>
> * Fix: Don't lose HTTP/2 flow control bytes when incoming data races with a stream close. If this
> happened enough then eventually the connection would stall.
>
> * Fix: Acknowledge and apply inbound HTTP/2 settings atomically. Previously we had a race where we
> could use new flow control capacity before acknowledging it, causing strict HTTP/2 servers to
> fail the call.
>
> * Fix: Recover gracefully when a coalesced connection immediately goes unhealthy.
>
> ## Version 3.14.2
>
> _2019-05-19_
>
> * Fix: Lock in a route when recovering from an HTTP/2 connection error. We had a bug where two
> calls that failed at the same time could cause OkHttp to crash with a `NoSuchElementException`
> instead of the expected `IOException`.
>
> * Fix: Don't crash with a `NullPointerException` when formatting an error message describing a
> truncated response from an HTTPS proxy.
>
>
> ## Version 3.14.1
>
> _2019-04-10_
>
> * Fix: Don't crash when an interceptor retries when there are no more routes. This was an
> edge-case regression introduced with the events cleanup in 3.14.0.
>
> * Fix: Provide actionable advice when the exchange is non-null. Prior to 3.14, OkHttp would
> silently leak connections when an interceptor retries without closing the response body. With
> ... (truncated)
Commits
- [`d02340f`](https://github.com/square/okhttp/commit/d02340f9dfac4ead42befc1a4d477b45401956cf) Prepare for release 4.2.2.
- [`b897fb8`](https://github.com/square/okhttp/commit/b897fb8e0f3fe3622633d59ecaf220ddcae5830f) Merge pull request [#5537](https://github-redirect.dependabot.com/square/okhttp/issues/5537) from square/jwilson.1006.cancel_close
- [`10f9227`](https://github.com/square/okhttp/commit/10f9227b9398d9c7651131bdeeae92bb714a3bb2) If RST STREAM and END OF STREAM race, send RST STREAM (4.2.x branch)
- [`97d25e8`](https://github.com/square/okhttp/commit/97d25e88b82454b128d1588c9c0bc013efeee7fe) Prepare next development version.
- [`57a165b`](https://github.com/square/okhttp/commit/57a165b69c6551c1caec8a557e0e9c9abf54b536) Prepare for release 4.2.1.
- [`4c640ad`](https://github.com/square/okhttp/commit/4c640ad6c3016f49e753b5c86ab5c4d8b072bb66) Merge pull request [#5524](https://github-redirect.dependabot.com/square/okhttp/issues/5524) from square/jwilson.1002.cherrypick_poolfix
- [`1b4b6bb`](https://github.com/square/okhttp/commit/1b4b6bbc82206816ced207bb0132611f770c56cd) Fix connection pooling for different clients with the same pool.
- [`582f8ef`](https://github.com/square/okhttp/commit/582f8ef2f78cf001d479cb65831674289fd83af0) Prepare for release 4.2.0.
- [`9b60ca8`](https://github.com/square/okhttp/commit/9b60ca8e88445de48997d3391ae15417a6ef5d90) Merge pull request [#5434](https://github-redirect.dependabot.com/square/okhttp/issues/5434) from square/jwilson.0909.race
- [`510475a`](https://github.com/square/okhttp/commit/510475a21586fdf6010312a1950dca6e87cb6d2e) Don't leak incoming bytes when we race incoming data and close
- Additional commits viewable in [compare view](https://github.com/square/okhttp/compare/parent-3.2.0...parent-4.2.2)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Bumps okhttp from 3.2.0 to 4.2.2.
Changelog
*Sourced from [okhttp's changelog](https://github.com/square/okhttp/blob/master/docs/changelog_3x.md).* > OkHttp 3.x Change Log > ===================== > > ## Version 3.14.4 > > _2019-09-29_ > > * Fix: Cancel calls that fail due to unexpected exceptions. We had a bug where an enqueued call > would never call back if it crashed with an unchecked throwable, such as a > `NullPointerException` or `OutOfMemoryError`. We now call `Callback.onFailure()` with an > `IOException` that reports the call as canceled. The triggering exception is still delivered to > the thread's `UncaughtExceptionHandler`. > * Fix: Don't evict incomplete entries when iterating the cache. We had a bug where iterating > `Cache.urls()` would prevent in-flight entries from being written. > > > ## Version 3.14.3 > > _2019-09-10_ > > * Fix: Don't lose HTTP/2 flow control bytes when incoming data races with a stream close. If this > happened enough then eventually the connection would stall. > > * Fix: Acknowledge and apply inbound HTTP/2 settings atomically. Previously we had a race where we > could use new flow control capacity before acknowledging it, causing strict HTTP/2 servers to > fail the call. > > * Fix: Recover gracefully when a coalesced connection immediately goes unhealthy. > > ## Version 3.14.2 > > _2019-05-19_ > > * Fix: Lock in a route when recovering from an HTTP/2 connection error. We had a bug where two > calls that failed at the same time could cause OkHttp to crash with a `NoSuchElementException` > instead of the expected `IOException`. > > * Fix: Don't crash with a `NullPointerException` when formatting an error message describing a > truncated response from an HTTPS proxy. > > > ## Version 3.14.1 > > _2019-04-10_ > > * Fix: Don't crash when an interceptor retries when there are no more routes. This was an > edge-case regression introduced with the events cleanup in 3.14.0. > > * Fix: Provide actionable advice when the exchange is non-null. Prior to 3.14, OkHttp would > silently leak connections when an interceptor retries without closing the response body. With > ... (truncated)Commits
- [`d02340f`](https://github.com/square/okhttp/commit/d02340f9dfac4ead42befc1a4d477b45401956cf) Prepare for release 4.2.2. - [`b897fb8`](https://github.com/square/okhttp/commit/b897fb8e0f3fe3622633d59ecaf220ddcae5830f) Merge pull request [#5537](https://github-redirect.dependabot.com/square/okhttp/issues/5537) from square/jwilson.1006.cancel_close - [`10f9227`](https://github.com/square/okhttp/commit/10f9227b9398d9c7651131bdeeae92bb714a3bb2) If RST STREAM and END OF STREAM race, send RST STREAM (4.2.x branch) - [`97d25e8`](https://github.com/square/okhttp/commit/97d25e88b82454b128d1588c9c0bc013efeee7fe) Prepare next development version. - [`57a165b`](https://github.com/square/okhttp/commit/57a165b69c6551c1caec8a557e0e9c9abf54b536) Prepare for release 4.2.1. - [`4c640ad`](https://github.com/square/okhttp/commit/4c640ad6c3016f49e753b5c86ab5c4d8b072bb66) Merge pull request [#5524](https://github-redirect.dependabot.com/square/okhttp/issues/5524) from square/jwilson.1002.cherrypick_poolfix - [`1b4b6bb`](https://github.com/square/okhttp/commit/1b4b6bbc82206816ced207bb0132611f770c56cd) Fix connection pooling for different clients with the same pool. - [`582f8ef`](https://github.com/square/okhttp/commit/582f8ef2f78cf001d479cb65831674289fd83af0) Prepare for release 4.2.0. - [`9b60ca8`](https://github.com/square/okhttp/commit/9b60ca8e88445de48997d3391ae15417a6ef5d90) Merge pull request [#5434](https://github-redirect.dependabot.com/square/okhttp/issues/5434) from square/jwilson.0909.race - [`510475a`](https://github.com/square/okhttp/commit/510475a21586fdf6010312a1950dca6e87cb6d2e) Don't leak incoming bytes when we race incoming data and close - Additional commits viewable in [compare view](https://github.com/square/okhttp/compare/parent-3.2.0...parent-4.2.2)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)