timeoutTask.cancel();
            }
        }

        return resultBuf.toString();

    }

    /**
     * Executes the Python script with the configured parameters.
     * Sets up the command list, working directory, and environment variables,
     * then starts the Python process and waits for completion.
     *

        assertNotSame(loginException.getMessageCode(), logoutException.getMessageCode());
    }

    public void test_complexMessageCode() {
        // Setup - test with a complex message code that has parameters
        final String errorDetail = "Authentication failed";
        final VaMessenger<FessMessages> complexMessageCode =

import jcifs.internal.util.SMBUtil;

/**
 * SMB Direct Negotiate Response message.
 *
 * As per MS-SMBD 2.2.2 - SMB_DIRECT_NEGOTIATE_RESPONSE
 * This message is sent in response to negotiate SMB Direct protocol parameters.
 */
public class SmbDirectNegotiateResponse {

    // Protocol constants
    /** SMB Direct negotiate response message type */
    public static final int NEGOTIATE_RESPONSE = 0x02;

## Benefits { #benefits }

When using the automatically generated clients, you would get **autocompletion** for:

* Methods.
* Request payloads in the body, query parameters, etc.
* Response payloads.

You would also have **inline errors** for everything.

     *
     * @param <T> the response type
     * @param request the request to send
     * @param response the response object to populate
     * @param params additional parameters for the request
     * @return the response
     * @throws IOException if an I/O error occurs
     */

        return getText(inputStream, params, null);
    }

    /**
     * Returns an extracted text.
     *
     * @param inputStream An input stream.
     * @param params A map of parameters.
     * @param postFilter A post filter.
     * @return An extracted data.
     */
    protected ExtractData getText(final InputStream inputStream, final Map<String, String> params,

///

It has all the information about the *path operation* and is used to generate the automatic documentation.

It includes the `tags`, `parameters`, `requestBody`, `responses`, etc.

This *path operation*-specific OpenAPI schema is normally generated automatically by **FastAPI**, but you can also extend it.

/// tip

This is a low level extension point.

    // PUT /api/admin/group
    /**
     * Returns list of group settings.
     * Supports both GET and PUT requests for retrieving paginated group configurations.
     *
     * @param body search parameters for filtering and pagination
     * @return JSON response containing group settings list with pagination info
     */
    @Execute
    public JsonResponse<ApiResult> settings(final SearchBody body) {

    /**
     * Retrieves boost document rule settings with pagination support.
     *
     * @param body the search body containing pagination and filter parameters
     * @return JSON response containing list of boost document rule configurations
     */
    // GET /api/admin/boostdoc
    // PUT /api/admin/boostdoc
    @Execute

///

⚫️ ✔️ 🌐 ℹ 🔃 *➡ 🛠️* & ⚙️ 🏗 🏧 🧾.

⚫️ 🔌 `tags`, `parameters`, `requestBody`, `responses`, ♒️.

👉 *➡ 🛠️*-🎯 🗄 🔗 🛎 🏗 🔁 **FastAPI**, ✋️ 👆 💪 ↔ ⚫️.

/// tip

👉 🔅 🎚 ↔ ☝.