_2016-07-10_

 *  **Fix a major bug in encoding HTTP headers.** In 3.4.0 and 3.4.0-RC1 OkHttp
    had an off-by-one bug in our HPACK encoder. This bug could have caused the
    wrong headers to be emitted after a sequence of HTTP/2 requests! Everyone
    who is using OkHttp 3.4.0 or 3.4.0-RC1 should upgrade for this bug fix.


## Version 3.4.0

_2016-07-08_

	<property name="maven.snapshot.repo.url" value="https://central.sonatype.com/repository/maven-snapshots" />
	<property name="maven.release.repo.url" value="https://maven.codelibs.org" />
	<property name="opensearch.version" value="3.4.0" />

	<target name="install.modules">
		<mkdir dir="${target.dir}" />
		<delete dir="${modules.dir}" />
		<mkdir dir="${modules.dir}" />

		<!-- analysis-common -->
		<antcall target="install.module">

   * https://github.com/jspecify/jspecify-reference-checker/blob/61aafa4ae52594830cfc2d61c8b113009dbdb045/src/main/java/com/google/jspecify/nullness/NullSpecTransfer.java#L789
   * and https://github.com/jspecify/jspecify/issues/490.
   *
   * (That would also have ensured that its cause was always an Error, rather than possibly another
   * kind of Throwable that was later passed to initCause. Then we could have declared the override

   * https://github.com/jspecify/jspecify-reference-checker/blob/61aafa4ae52594830cfc2d61c8b113009dbdb045/src/main/java/com/google/jspecify/nullness/NullSpecTransfer.java#L789
   * and https://github.com/jspecify/jspecify/issues/490.
   *
   * (That would also have ensured that its cause was always an Error, rather than possibly another
   * kind of Throwable that was later passed to initCause. Then we could have declared the override

            throwTooLongBoundarySizeException(contentType, boundarySize, limitSize);
        }
    }

    protected int getBoundaryLimitSize() {
        // one HTTP proxy tool already limits the size (e.g. 3450 bytes)
        // so specify this size for test
        return 2000; // you can override as you like it
    }

[OkHttp311]: https://square.github.io/okhttp/changelog_3x/#version-320
[OkHttp312]: https://square.github.io/okhttp/changelog_3x/#version-330
[OkHttp313]: https://square.github.io/okhttp/changelog_3x/#version-340
[OkHttp314]: https://square.github.io/okhttp/changelog_3x/#version-310
[OkHttp35]: https://square.github.io/okhttp/changelog_3x/#version-350

    void testDecodeWithNonZeroBufferIndex() throws SMBProtocolDecodingException {
        // Prepare test data with offset
        int offset = 10;
        byte[] buffer = new byte[34]; // 10 offset + 16 header + 8 data
        int bufferIndex = offset;

        // Set up test values
        int namedPipeState = 0x02;
        int readDataAvailable = 256;
        int numberOfMessages = 5;

    @Mock
    private MessageDigest mockMd5;

    @BeforeEach
    void setUp() throws NoSuchAlgorithmException {
        // Mock Crypto.getMD5() to return our mockMd5 instance
        // This requires Mockito 3.4.0+ for MockedStatic
        // For simplicity, we'll assume Crypto.getMD5() is static and mock it.
        // If it's not static, we'd need to inject it or mock the class that provides it.

- go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp: v0.58.0 → v0.61.0
- go.opentelemetry.io/otel/metric: v1.35.0 → v1.36.0
- go.opentelemetry.io/otel/sdk/metric: v1.34.0 → v1.36.0
- go.opentelemetry.io/otel/sdk: v1.34.0 → v1.36.0
- go.opentelemetry.io/otel/trace: v1.35.0 → v1.36.0
- go.opentelemetry.io/otel: v1.35.0 → v1.36.0
- go.yaml.in/yaml/v2: v2.4.2 → v2.4.3
- golang.org/x/crypto: v0.36.0 → v0.45.0

 *  Fix in `okhttp-coroutines`: Don't leak response bodies in `executeAsync()`. We had a bug where
    we didn't call `Response.close()` if the coroutine was canceled before its response was
    returned.

 *  Upgrade: [Okio 3.9.0][okio_3_9_0].

 *  Upgrade: [Kotlin 1.9.23][kotlin_1_9_23].

 *  Upgrade: [Unicode® IDNA 15.1.0][idna_15_1_0]


## Version 5.0.0-alpha.12

_2023-12-17_