* monitors their progress, and handles cleanup operations.
     *
     * <p>The method:</p>
     * <ul>
     *   <li>Creates crawler threads for each data configuration</li>
     *   <li>Manages concurrent execution based on thread count limits</li>
     *   <li>Monitors thread completion and handles cleanup</li>
     *   <li>Records execution timing and statistics</li>
     * </ul>

        // Just verify that contexts were written
        assertTrue(bytesWritten > 60); // Should be larger than basic negotiate request
    }

    @Test
    @DisplayName("Should handle empty negotiate contexts array")
    void testWriteBytesWireFormatEmptyContexts() {
        // Given
        when(mockConfig.getMaximumVersion()).thenReturn(DialectVersion.SMB302);

        NtlmMessage.writeULong(dest, 0, 0x01020304);
        assertArrayEquals(new byte[] { 4, 3, 2, 1 }, dest, "Writer must be little‑endian");
    }

    @Test
    @DisplayName("writeULong handles negative values as unsigned")
    void testWriteULongNegative() {
        byte[] dest = new byte[4];
        NtlmMessage.writeULong(dest, 0, -1);

## Zugriff auf den Requestbody in einem Exceptionhandler { #accessing-the-request-body-in-an-exception-handler }

/// tip | Tipp

Um dasselbe Problem zu lösen, ist es wahrscheinlich viel einfacher, den `body` in einem benutzerdefinierten Handler für `RequestValidationError` zu verwenden ([Fehlerbehandlung](../tutorial/handling-errors.md#use-the-requestvalidationerror-body)).

        assertEquals("FFFE80", Hexdump.toHexString(data2, 0, 6)); // 6 chars = 3 bytes
        assertEquals("FFFE807F", Hexdump.toHexString(data2, 0, 8)); // 8 chars = 4 bytes

        // Test odd size (should handle correctly)
        byte[] data3 = { 0x0A, 0x0B, 0x0C };
        assertEquals("0", Hexdump.toHexString(data3, 0, 1)); // 1 char = 0.5 bytes (rounds up to 1)

            assertEquals(2048L * 4 * 4096, fileFsSizeInfo.getCapacity());
            assertEquals(1024L * 4 * 4096, fileFsSizeInfo.getFree());
        }

        @Test
        @DisplayName("Should handle negative values in buffer")
        void shouldHandleNegativeValuesInBuffer() throws SMBProtocolDecodingException {
            // Given - negative values (treated as unsigned in protocol)

                .longOpt("ignore-transitive-repositories")
                .desc("If set, Maven will ignore remote repositories introduced by transitive dependencies.")
                .build());

        // Parameters handled by script
        options.addOption(Option.builder()
                .longOpt(DEBUG)
                .desc("Launch the JVM in debug mode (script option).")
                .build());

{* ../../docs_src/response_model/tutorial003_02_py310.py hl[8,10:11] *}

This simple case is handled automatically by FastAPI because the return type annotation is the class (or a subclass of) `Response`.

     * Default constructor for SearchForm.
     */
    public SearchForm() {
    }

    /**
     * The name field for searching data configurations.
     */
    public String name;

    /**
     * The handler name field for searching data configurations.
     */
    public String handlerName;

    /**
     * The description field for searching data configurations.
     */
    public String description;

import jcifs.SmbTreeHandle;

/**
 * Internal interface for SMB tree handle operations.
 *
 * This interface provides internal methods for managing
 * SMB tree connections and their lifecycle.
 *
 * @author mbechler
 */
public interface SmbTreeHandleInternal extends SmbTreeHandle {

    /**
     * Releases this tree handle back to the pool for reuse
     */
    void release();

    /**