schedule: # Runs the action weekly on Monday at 3:42 UTC
    - cron: '42 3 * * 1'

permissions:
  contents: write
  pull-requests: write

jobs:
  update-jdks:
    if: github.repository == 'gradle/gradle'
    permissions:
      contents: write
      pull-requests: write
    runs-on: ubuntu-latest
    steps:
      - name: Checkout repository
        uses: actions/checkout@v6
        with:

                }
            }
            response.sendError(statusCode, message);
        }
    }

    /**
     * Processes API requests to the search engine.
     * Handles both regular API calls and plugin requests.
     *
     * @param request  the HTTP servlet request
     * @param response the HTTP servlet response
     * @param path     the request path after removing the prefix

/**
 * Servlet filter for handling character encoding conversion and URL redirection.
 * This filter processes requests with specific encoding requirements and converts
 * character encodings according to configured mapping rules.
 *
 * <p>The filter intercepts requests matching configured path patterns and
 * redirects them with proper character encoding applied to parameters.</p>
 */

The daemon never runs any user code in the background.

There are several different types of requests, such as a request to run a set of tasks, or to query a tooling model, or to stop.
Some requests will require that the build is configured and maybe some work executed, and other requests might not.

See [Build execution model](build-execution-model.md) for more details.

### Build state model

on:
  pull_request:
    types: [opened]

permissions: {}

jobs:
  add-reviews:
    permissions:
      contents: read  # for kentaro-m/auto-assign-action to fetch config file
      pull-requests: write  # for kentaro-m/auto-assign-action to assign PR reviewers
    runs-on: ubuntu-latest
    steps:

name: Check pulls metadata

on:
  pull_request_target:
    types: [ closed, unlabeled, milestoned, demilestoned ]

permissions: {}

jobs:
  check_pull_metadata:
    permissions:
      issues: write
      pull-requests: write
    runs-on: ubuntu-latest
    steps:
      # Check that PRs have proper metadata: labels and milestone
      # https://github.com/gradle/issue-management-action/blob/main/src/pull-metadata.ts

import jakarta.servlet.http.HttpServletRequest;
import jakarta.servlet.http.HttpServletResponse;

/**
 * Filter for CPU load-based request control.
 * Returns HTTP 429 (Too Many Requests) when CPU usage exceeds configurable thresholds.
 * Web and API requests have independent threshold settings.
 */
public class LoadControlFilter implements Filter {

    private static final Logger logger = LogManager.getLogger(LoadControlFilter.class);

 * for API endpoints including authentication, message handling, and access control.
 *
 * This class extends FessBaseAction and provides specialized behavior for API requests,
 * including token-based authentication and JSON response handling.
 */
public abstract class FessApiAction extends FessBaseAction {

    /**
     * Default constructor.
     */
    public FessApiAction() {

 */
package org.codelibs.fess.sso;

/**
 * Represents the type of SSO (Single Sign-On) response being requested.
 * This enum is used to differentiate between various SSO operations,
 * such as metadata requests and logout actions.
 */
public enum SsoResponseType {
    /**
     * Indicates a request for SSO metadata, which is typically used for
     * configuration and discovery in protocols like SAML.
     */
    METADATA,

4. The daemon runs the request, sending back data such as logging output or tooling API events and intermediate models while doing so.
5. The daemon sends the result back. For some requests, this might be a simple success/failure result, and for others this might also include a more complex object, such as a tooling API model.