* </ul>
 *
 * <p>The {@link TextNormalizeContext} class provides a fluent API to configure the text
 * normalization process, including setting initial buffer capacity, maximum term sizes,
 * duplicate term removal, and custom space characters.
 *
 * <p>Example usage:
 * <pre>{@code
 * Reader reader = new StringReader("Example text to normalize.");
 * String normalizedText = TextUtil.normalizeText(reader)

        // Note: getType() method does not exist in Type1Message
        assertTrue(type1.getFlags() != 0); // Should have some flags set
    }

    @Test
    @DisplayName("Should create Type 1 message with custom flags")
    void testType1MessageWithFlags() {
        // Given
        int flags =
                NtlmFlags.NTLMSSP_NEGOTIATE_UNICODE | NtlmFlags.NTLMSSP_NEGOTIATE_NTLM | NtlmFlags.NTLMSSP_NEGOTIATE_OEM_DOMAIN_SUPPLIED;

До FastAPI 0.106.0 вызывать исключения после `yield` было невозможно: код после `yield` в зависимостях выполнялся уже после отправки ответа, поэтому [Обработчики исключений](../tutorial/handling-errors.md#install-custom-exception-handlers){.internal-link target=_blank} к тому моменту уже отработали.

  /*
   * Under Android, MyError propagates up and fails the test?
   *
   * TODO(b/218700094): Does this matter to prod users, or is it just a feature of our testing
   * environment? If the latter, maybe write a custom Executor that avoids failing the test when it
   * sees an Error?
   */
  @AndroidIncompatible
  public void testTaskThrowsError() throws Exception {
    class MyError extends Error {}

 * fragile because they assume that only certain methods will be called and because they often
 * implement subtleties of the API improperly.
 *
 * <p><b>Custom implementation</b>: Avoid implementing {@code ListenableFuture} from scratch. If you
 * can't get by with the standard implementations, prefer to derive a new {@code Future} instance

 * fragile because they assume that only certain methods will be called and because they often
 * implement subtleties of the API improperly.
 *
 * <p><b>Custom implementation</b>: Avoid implementing {@code ListenableFuture} from scratch. If you
 * can't get by with the standard implementations, prefer to derive a new {@code Future} instance

        this(witnessServer, context, new WitnessRpcClient(witnessServer, context));
    }

    /**
     * Creates a new witness client with a custom RPC client (for testing).
     *
     * @param witnessServer the witness server address
     * @param context the CIFS context
     * @param rpcClient the RPC client to use
     */

                .filter(k -> k != null && k.toString().startsWith(Constants.SYSTEM_PROP_PREFIX))
                .forEach(k -> addSystemProperty(cmdList, k.toString(), null, null));
    }

    /**
     * Adds custom system properties that match the given regex pattern to the command list.
     *
     * @param cmdList the command list to add properties to
     * @param regex the regular expression pattern to match property names
     */

     *
     * @return a list of argument strings
     */
    @Nonnull
    List<String> args();

    /**
     * Per-request {@link Lookup} for customization.
     *
     * @return a lookup possibly with custom components
     */
    @Nonnull
    Lookup lookup();

    /**
     * Returns the current working directory for the Maven execution.
     * If not explicitly set, this value will be detected during parsing.

    - [**API Machinery**](#api-machinery-3)
      - [**Admission Control**](#admission-control)
      - [**API & API server**](#api-&-api-server)
      - [**Audit**](#audit)
      - [**Custom Resources**](#custom-resources)
      - [**Other**](#other)
    - [**Apps**](#apps-1)
    - [**Auth**](#auth-3)
      - [**Audit**](#audit-1)
      - [**RBAC**](#rbac)
      - [**Other**](#other-1)
      - [**GCE**](#gce)