*
     * @param handle the DCE/RPC handle for communication
     * @param server the server name (null defaults to local server)
     * @param access the desired access rights
     * @throws IOException if an I/O error occurs during handle creation
     */
    public SamrPolicyHandle(final DcerpcHandle handle, String server, final int access) throws IOException {
        this.handle = handle;
        if (server == null) {

    }

    /**
     * Sets the context handle for unregistration.
     *
     * @param contextHandle the context handle from registration
     */
    public void setContextHandle(byte[] contextHandle) {
        this.contextHandle = contextHandle != null ? contextHandle.clone() : null;
    }

    /**
     * Gets the context handle.
     *
     * @return the context handle
     */
    public byte[] getContextHandle() {

        }

        @Test
        @DisplayName("Should handle null file ID in setter")
        void testSetNullFileId() {
            assertDoesNotThrow(() -> request.setFileId(null));
        }

        @Test
        @DisplayName("Should handle various file ID sizes")
        void testVariousFileIdSizes() {
            byte[] shortFileId = new byte[8];

- Fix kube-apiserver startup to wait for APIServices to be installed into the HTTP handler before reporting readiness. ([#89147](https://github.com/kubernetes/kubernetes/pull/89147), [@sttts](https://github.com/sttts)) [SIG API Machinery]

            return new LeaseV2CreateContextResponse();
        case "DHnQ": // Durable Handle Request/Response
            return new jcifs.internal.smb2.persistent.DurableHandleResponse();
        case "DH2Q": // Durable Handle V2 Request/Response
            return new jcifs.internal.smb2.persistent.DurableHandleV2Response();
        case "DHnC": // Durable Handle Reconnect Request/Response

`@ExperimentalOkHttpApi`. You can safely use this release in production.

 *  Fix: Attempt to read the response even if sending the request failed. This makes it possible
    to handle response statuses like `HTTP/1.1 431 "Request Header Fields Too Large`.

 *  Fix: Handle multiple 1xx responses.

 *  Fix: Address a performance bug in our internal task runner. We had a race condition that could

        assertFalse(target.isOpen());
        assertFalse(target.isStale());

        // After ensureOpen, handle valid -> open
        SmbFileHandleImpl fh = target.ensureOpen();
        assertSame(fileHandle, fh);
        assertTrue(target.isOpen());
        assertFalse(target.isStale());

        // If handle becomes invalid, reflect stale

         *
         * @param handle the policy handle to close
         */
        public LsarClose(final rpc.policy_handle handle) {
            this.handle = handle;
        }

        @Override
        public void encode_in(final NdrBuffer _dst) throws NdrException {
            this.handle.encode(_dst);
        }

        @Override

        }

        @Test
        @DisplayName("Should handle special SMB2 context names")
        void testSMB2ContextNames() {
            // Common SMB2 create context names
            String[] contextNames = { "DHnQ", // Durable handle request
                    "DHnC", // Durable handle reconnect
                    "AlSi", // Allocation size
                    "MxAc", // Max access

    }

    @Test
    @DisplayName("Should handle null hostname in getByName")
    void testGetByNameWithNull() {
        // When/Then
        assertThrows(UnknownHostException.class, () -> {
            nameServiceClient.getByName(null);
        }, "Should throw UnknownHostException for null hostname");
    }

    @Test
    @DisplayName("Should handle empty hostname in getByName")
    void testGetByNameWithEmpty() {