- Traffic to a service IP now starts getting rejected (as opposed to
      merely dropped) as soon as there are no longer any *usable*
      endpoints, rather than waiting until all of the terminating
      endpoints have terminated even when those terminating endpoints
      were not being used.
  
    - Chains for endpoints that won't be used are no longer output to

        assertEquals('S', messageBytes[4]);
        assertEquals('S', messageBytes[5]);
        assertEquals('P', messageBytes[6]);
        assertEquals(0, messageBytes[7]); // Null terminator
    }

    @Test
    @DisplayName("Should include message type indicator")
    void testMessageTypeIndicator() throws IOException {
        // When
        Type1Message type1 = new Type1Message(mockContext);

Since HTTP requests frequently happen in parallel, connection pooling must be thread-safe.

These are the primary classes involved with establishing, sharing, and terminating connections:

 * **RealConnectionPool** manages reuse of HTTP and HTTP/2 connections for reduced latency. Every OkHttpClient has one, and its lifetime spans the lifetime of the OkHttpClient.

    /**
     * Determines whether this resource represents a workgroup reference.
     *
     * @return whether this is a workgroup reference
     * @throws CIFSException if the determination cannot be made
     */
    boolean isWorkgroup() throws CIFSException;

    /**
     * Determines whether this resource represents the root of the SMB hierarchy.
     *

            buffer[serviceBytes.length] = 0; // Null terminator

            // When
            int bytesRead = (int) invokeMethod(response, "readBytesWireFormat", new Class[] { byte[].class, int.class }, buffer, 0);

            // Then
            assertEquals(serviceBytes.length + 1, bytesRead, "Should read service string plus terminator");

  the Job controller now does not consider a terminating Pod (a pod that has a `.metadata.deletionTimestamp`)
  as a failure until that Pod is terminal (its `.status.phase` is `Failed` or `Succeeded`).
  
  However, the Job controller creates a replacement Pod as soon as the termination becomes apparent.

        assertEquals('S', (char) type2Bytes[4]);
        assertEquals('S', (char) type2Bytes[5]);
        assertEquals('P', (char) type2Bytes[6]);
        assertEquals(0, type2Bytes[7]); // Null terminator
        assertEquals(2, type2Bytes[8], "Message type should be 2"); // Type 2

        // Verify response status
        verify(mockResponse).setStatus(HttpServletResponse.SC_UNAUTHORIZED);

                assertNotNull(targetInfo);
                // Should only contain server info - but might have different structure than expected
                assertTrue(targetInfo.length >= 4, "Target info should have at least terminator");
                // Check if it contains server info (implementation dependent)
                if (targetInfo.length > 4) {
                    assertEquals(1, Type2Message.readUShort(targetInfo, 0)); // Type 0x0001

        String testString = "Hello World";
        ndrBuffer.enc_ndr_string(testString);

        // Expected length: 4 (actual_count) + 4 (offset) + 4 (max_count) + len*2 (unicode) + 2 (null terminator)
        int expectedLength = 4 + 4 + 4 + (testString.length() * 2) + 2;
        assertEquals(expectedLength, ndrBuffer.getIndex());
        assertEquals(expectedLength, ndrBuffer.getLength());

        assertEquals('S', messageBytes[4]);
        assertEquals('S', messageBytes[5]);
        assertEquals('P', messageBytes[6]);
        assertEquals(0, messageBytes[7]); // Null terminator
    }

    @Test
    @DisplayName("Should include message type indicator")
    void testMessageTypeIndicator() throws Exception {
        // Given
        Type2Message type2 = createMockType2Message();