});
        }
    }

    @Nested
    @DisplayName("Integration tests")
    class IntegrationTests {

        @Test
        @DisplayName("Should handle complete read-write cycle")
        void testCompleteReadWriteCycle() throws SMBProtocolDecodingException {
            // Given
            byte[] writeBuffer = new byte[100];
            byte[] readBuffer = new byte[100];

Elas tendem a exigir configurações mais complexas, um gerenciador de fila de mensagens/tarefas, como RabbitMQ ou Redis, mas permitem executar tarefas em segundo plano em vários processos e, especialmente, em vários servidores.

* Validación de datos
* Documentación automática

## Tipos especiales y validación { #special-types-and-validation }

Además de tipos singulares normales como `str`, `int`, `float`, etc., puedes usar tipos singulares más complejos que heredan de `str`.

Para ver todas las opciones que tienes, Revisa [Resumen de tipos de Pydantic](https://docs.pydantic.dev/latest/concepts/types/). Verás algunos ejemplos en el siguiente capítulo.

    awaitDone(() -> ref.get() == null);
  }

  /**
   * Tries to perform a "full" garbage collection cycle (including processing of weak references and
   * invocation of finalize methods) and waits for it to complete. Ensures that at least one weak
   * reference has been cleared and one {@code finalize} method has been run before this method
   * returns. This method may be useful when testing the garbage collection mechanism itself, or

                    smbComTreeDisconnect.toString();
                }
            });
            threads[i].start();
        }

        // Wait for all threads to complete
        for (Thread thread : threads) {
            thread.join();
        }

        // Then - no exceptions should have been thrown
        assertTrue(true); // If we reach here, no exceptions occurred
    }

Enviar um corpo em uma requisição `GET` não tem um comportamento definido nas especificações, porém é suportado pelo FastAPI, apenas para casos de uso bem complexos/extremos.

Como é desencorajado, a documentação interativa com Swagger UI não irá mostrar a documentação para o corpo da requisição ao usar `GET`, e proxies intermediários podem não suportá-lo.

///

    /**
     * Initializes the query field configuration by loading field mappings from FessConfig.
     * This method is called after dependency injection is complete.
     * It sets up response fields, search fields, facet fields, sort fields, and other
     * field configurations based on the application configuration.
     */
    @PostConstruct
    public void init() {

   * body, which it will attempt to do otherwise:
   *
   *  * Don't cache the response. The cache will try to read the entire response body so that it
   *    can successfully complete the cache entry.
   *
   *  * Throttle the response. The HTTP/1 connection pool will attempt to read the entire response
   *    body so that it can pool the connection.
   */

                Encdec.enc_uint16le((short) 50, buffer, 8); // Fragment length
                return 30; // Initial bytes received
            });

            // Mock second receive to complete fragment
            when(mockSmbPipeHandleInternal.recv(buf, 30, 20)).thenReturn(20);

            int result = handle.doReceiveFragment(buf);
            assertEquals(50, result);

 * <p>
 * To fully understand the information exposed by this class a description
 * of the access check algorithm used by Windows is required. The following
 * is a basic description of the algorithm. For a more complete description
 * we recommend reading the section on Access Control in Keith Brown's
 * "The .NET Developer's Guide to Windows Security" (which is also
 * available online).
 * <p>