// Given
        when(request.isResponseAsync()).thenReturn(true);
        when(request.size()).thenReturn(100);
        when(request.getOverrideTimeout()).thenReturn(3000);
        when(request.allowChain(any())).thenReturn(true);

        // When
        boolean async = request.isResponseAsync();
        int size = request.size();
        Integer timeout = request.getOverrideTimeout();

 * parameter.
 * </p>
 *
 * <p>
 * The reader uses a queue to buffer documents read from Elasticsearch, and it retries failed requests
 * up to a maximum number of times.
 * </p>
 *
 * <p>
 * <b>Usage:</b>
 * </p>
 * <pre>
 * {@code
 * Client client = // Obtain Elasticsearch client
 * SuggestSettings settings = // Obtain SuggestSettings

- Fixes a regression in v1beta1 PodDisruptionBudget handling of `strategic merge patch`-type API requests for the `selector` field. Prior to 1.21, these requests would merge `matchLabels` content and replace `matchExpressions` content. In 1.21, patch requests touching the `selector` field started replacing the entire selector. This is consistent with server-side apply and the v1 PodDisruptionBudget behavior, but should not have...

    @Resource
    protected SuggestHelper suggestHelper;

    // GET /api/admin/elevateword
    // PUT /api/admin/elevateword
    /**
     * Returns list of elevate word settings.
     * Supports both GET and PUT requests for retrieving paginated elevate word configurations.
     *
     * @param body search parameters for filtering and pagination
     * @return JSON response containing elevate word settings list with pagination info
     */

- Kube-apiserver: fixes a 1.27+ regression in watch stability by serving watch requests without a resourceVersion from the watch cache by default, as in <1.27 (disabling the change in #115096 by default). This mitigates the impact of an etcd watch bug (https://github.com/etcd-io/etcd/pull/17555). If the 1.27 change in #115096 to serve these requests from underlying storage is still desired despite the impact on watch stability, it can be re-enabled with a `Watc...

- Fixed bugs in handling of server-side apply, create, and update API requests for objects containing duplicate items in keyed lists.
  - A `create` or `update` API request with duplicate items in a keyed list no longer wipes out managedFields. Examples include env var entries with the same name, or port entries with the same containerPort in a pod spec.

     *
     * @param req
     *            The servlet request
     * @param resp
     *            The servlet response
     * @param skipAuthentication
     *            If true the negotiation is only done if it is
     *            initiated by the client (MSIE post requests after successful NTLM SSP
     *            authentication). If false and the user has not been authenticated yet

* Add apiserver metric for number of requests dropped because of inflight limit. ([#58340](https://github.com/kubernetes/kubernetes/pull/58340), [@gmarek](https://github.com/gmarek))
* Add apiserver metric for current inflight-request usage. ([#58342](https://github.com/kubernetes/kubernetes/pull/58342), [@gmarek](https://github.com/gmarek))

    /** Client for RAG chat functionality. */
    @Resource
    protected ChatClient chatClient;

    /** The HTTP servlet request object for the current request. */
    @Resource
    protected HttpServletRequest request;

    /** Flag indicating whether search logging is enabled. */
    protected boolean searchLogSupport;

            final Credentials credentials = p.getSecond();
            scheme.authenticate(credentials, (request, consumer) -> {

                // request header
                for (final Header header : requestHeaderList) {
                    request.addHeader(header);
                }

                HttpEntity httpEntity = null;
                try {