Bump com.github.mizosoft.methanol:methanol from 1.7.0 to 1.8.4

[dependabot]

Bumps com.github.mizosoft.methanol:methanol from 1.7.0 to 1.8.4.

Release notes

Sourced from com.github.mizosoft.methanol:methanol's releases.

v1.8.4

• Fixed #129, where streaming large files through WritableBodyPublisher on slow networks caused high memory usage. Now the publisher blocks writers when the upload speed can't keep up. Memory usage is bounded according to the expression:

  int memoryQuota = Integer.getInteger("com.github.mizosoft.methanol.flow.prefetch", 8) * Integer.getInteger("jdk.httpclient.bufsize", 16 * 1024);

  Note that this also reflects on MoreBodyPublishers::ofOutputStream & MoreBodyPublishers::ofWritableByteChannel.

• Fixed #134, where the system language affected how HTTP dates were formatted.

v1.8.3

• Fixed #121, where the response body was retained throughout the entire read timeout, resulting in a "timed" memory leak. This happened as the previously used JVM-wide scheduler retained references to timeout tasks (which retained references to the response body through a reference chain starting from TimeoutBodySubscriber). Methanol now uses a library-wide scheduler (unless overridden by Methanol.Builder::readTimeout) that loses references to timeout tasks when invalidated.

• Fixed #125, where exception causes where swallowed in sync calls.

v1.8.2

• Fix regression caused by #118.

v1.8.1

• Fixed #117, where decompressing the response could potentially hang.

v1.8.0

Ok, here we go. That took a while.

There's been a number of unreleased features brewing in the last two and a half years (!). Guess I could say I've been cooking some Meth—anol, and now it's ready to serve. What's—my—name? Please don't say Heisenbug.

Anyhow, here's what's new:

• Added a Redis storage backend for the HTTP cache, which supports Standalone & Cluster setups.
• Added the ability to chain caches with different storage backends, expectedly in the order of decreasing locality. This will work well with the Redis cache. Consider the case where you have multiple instances of your service all sharing a Redis setup, you can have a chain of (JVM memory -> Redis) or even (JVM memory -> disk -> Redis) caches, so each node can have a local cache to consult first, and the shared Redis cache after.
• The object mapping mechanism has been reworked to stay away from ServiceLoader & static state. We now have an AdapterCodec that is registered per-client.

  var mapper = new JsonMapper();
  var adapterCodec =
      AdapterCodec.newBuilder()
          .encoder(JacksonAdapterFactory.createJsonEncoder(mapper))
          .decoder(JacksonAdapterFactory.createJsonDecoder(mapper))
          .build();
  var client =
      Methanol.newBuilder()
          .adapterCodec(adapterCodec)
          .build();
  record Person(String name) {}
  HttpResponse<Person> response = client.send(
  MutableRequest.GET(".../echo", new Person("Jack Reacher"), MediaType.APPLICATION_JSON),
  Person.class);

... (truncated)

Changelog

Sourced from com.github.mizosoft.methanol:methanol's changelog.

Version 1.8.4

• Fixed #129, where streaming large files through WritableBodyPublisher on slow networks caused high memory usage. Now the publisher blocks writers when the upload speed can't keep up. Memory usage is bounded according to the expression:

  int memoryQuota = Integer.getInteger("com.github.mizosoft.methanol.flow.prefetch", 8) * Integer.getInteger("jdk.httpclient.bufsize", 16 * 1024);

  Note that this also reflects on MoreBodyPublishers::ofOutputStream & MoreBodyPublishers::ofWritableByteChannel.

• Fixed #134, where the system language affected how HTTP dates were formatted.

Version 1.8.3

• Fixed #121, where the response body was retained throughout the entire read timeout, resulting in a "timed" memory leak. This happened as the previously used JVM-wide scheduler retained references to timeout tasks (which retained references to the response body through a reference chain starting from TimeoutBodySubscriber). Methanol now uses a library-wide scheduler that loses references to timeout tasks when invalidated.

• Fixed #125, where exception causes where swallowed in sync calls.

Version 1.8.2

Fix regression caused by #118.

Version 1.8.1

Fixed #117, where decompressing the response could potentially hang.

Version 1.8.0

Ok, here we go. That took a while.

There's been a number of unreleased features brewing in the last two and a half years (!). Guess I could say I've been cooking some Meth—anol, and now it's ready to serve. What's—my—name? Please don't say Heisenbug.

Anyhow, here's what's new:

• Added a Redis storage backend for the HTTP cache, which supports Standalone & Cluster setups.
• Added the ability to chain caches with different storage backends, expectedly in the order of decreasing locality. This will work well with the Redis cache. Consider the case where you have multiple instances of your service all sharing a Redis setup, you can have a chain of (JVM memory -> Redis) or even (JVM memory -> disk -> Redis) caches, so each node can have a local cache to consult first, and the shared Redis cache after.
• The object mapping mechanism has been reworked to stay away from ServiceLoader & static state. We now have an AdapterCodec that is registered per-client.

  var mapper = new JsonMapper();
  var adapterCodec =
      AdapterCodec.newBuilder()
          .encoder(JacksonAdapterFactory.createJsonEncoder(mapper))
          .decoder(JacksonAdapterFactory.createJsonDecoder(mapper))
          .build();
  var client =

... (truncated)

Commits

• 2aa9dc4 Release 1.8.4
• a364893 Fix releasing for Kotlin projects
• 491f4b8 Polish documentation
• 9846d59 Update gradle
• 99837af Remove unused function
• 52b6899 Add link for multipart uploads in README (#153)
• d5b6e81 Clarify java requirements at build and runtime (#143)
• 47c0148 Don't run tests on Mac with @​DisabledOnOs (#148)
• 74fb2e6 Skip running tests of methanol-brotli on aarch64 (#144)
• ef11a60 Modify workflows for fork PRs (#147)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Superseded by #204.