*/
package jcifs.internal.fscc;

import java.nio.charset.StandardCharsets;

import jcifs.Encodable;
import jcifs.internal.util.SMBUtil;

/**
 * File System Control Code (FSCC) request for pipe wait operations.
 * Implements the FSCTL_PIPE_WAIT control code used to wait for a named pipe
 * to become available when attempting to connect to a busy pipe.
 *
 * @author mbechler
 */

     * This method is called automatically when using try-with-resources statements.
     *
     * <p>The default implementation does nothing. Subclasses should override this method
     * if they need to perform cleanup operations.</p>
     *
     * @throws InvokerException if an error occurs while closing the {@link Invoker}
     */
    @Override
    default void close() throws InvokerException {}

## About security, APIs, and docs { #about-security-apis-and-docs }

Hiding your documentation user interfaces in production *shouldn't* be the way to protect your API.

That doesn't add any extra security to your API, the *path operations* will still be available where they are.

If there's a security flaw in your code, it will still exist.

import jcifs.dcerpc.ndr.NdrException;
import jcifs.dcerpc.ndr.NdrObject;

/**
 * Security Account Manager Remote (SAMR) protocol implementation.
 * This class provides DCE/RPC interface for SAM database operations including
 * user account management, group operations, and domain security functions.
 */
@SuppressWarnings("all")
public class samr {

    /**
     * Private constructor to prevent instantiation of utility class.
     */

import jcifs.smb1.dcerpc.ndr.NdrObject;

/**
 * Security Account Manager Remote (SAMR) protocol implementation for SMB1.
 * This class provides DCE/RPC interface for SAM database operations including
 * user account management, group operations, and domain security functions.
 */
public class samr {

    /**
     * Private constructor to prevent instantiation of utility class.
     */
    private samr() {

import com.google.common.collect.testing.features.CollectionSize;
import com.google.errorprone.annotations.CanIgnoreReturnValue;
import org.junit.Ignore;

/**
 * A generic JUnit test which tests conditional {@code setCount()} operations on a multiset. Can't
 * be invoked directly; please see {@link MultisetTestSuiteBuilder}.
 *
 * @author Chris Povirk
 */
@GwtCompatible

 * or implied. See the License for the specific language governing permissions and limitations under
 * the License.
 */
package com.google.common.collect;

import static com.google.common.collect.Iterators.emptyIterator;

import com.google.common.annotations.GwtCompatible;
import com.google.common.annotations.GwtIncompatible;
import com.google.common.annotations.J2ktIncompatible;
import java.io.InvalidObjectException;

## Cloud Scale Deployment

        assertTrue(response instanceof ServerMessageBlock2);
        assertTrue(response instanceof CommonServerMessageBlockResponse);
    }

    @Test
    @DisplayName("Should handle multiple read operations")
    void testMultipleReads() throws SMBProtocolDecodingException {
        // Given
        byte[] buffer1 = new byte[256];
        byte[] buffer2 = new byte[256];

Para desativá-los, defina suas URLs como `None` ao criar seu aplicativo `FastAPI`:

{* ../../docs_src/custom_docs_ui/tutorial001.py hl[8] *}

### Incluir a documentação personalizada

Agora você pode criar as *operações de rota* para a documentação personalizada.

Você pode reutilizar as funções internas do FastAPI para criar as páginas HTML para a documentação e passar os argumentos necessários: