},
      "scriptData": {
        "type": "keyword"
      },
      "crawler": {
        "type": "boolean"
      },
      "jobLogging": {
        "type": "boolean"
      },
      "available": {
        "type": "boolean"
      },
      "sortOrder": {
        "type": "integer"
      },
      "createdBy": {
        "type": "keyword"
      },
      "createdTime": {
        "type": "long"

    public String intervalTime;

    /**
     * Search criteria: boost value.
     */
    public String boost;

    /**
     * Search criteria: availability status.
     */
    public String available;

    /**
     * Search criteria: sort order.
     */
    public String sortOrder;

    /**
     * Search criteria: creator user.
     */
    public String createdBy;

    /**

        printStream.accept("Goals:");
        printStream.accept("  help  - display this help message");
        printStream.accept("  check - check for available upgrades");
        printStream.accept("  apply - apply available upgrades");
        printStream.accept("");
        printStream.accept("Options:");
        printStream.accept("  -m, --model-version <version> Target POM model version (4.0.0 or 4.1.0)");

        log.info("Setting up Samba container for SMB integration tests");

        // Check if Docker is available
        assumeTrue(isDockerAvailable(), "Docker is not available - skipping integration tests");
        assumeTrue(sambaContainer != null, "Container not initialized - Docker not available");

        // Create temporary directory structure for SMB shares
        tempDir = Files.createTempDirectory("smbtest");

    repo uses the file:// protocol, and it doesn't refer to a shared
    filesystem, it will continue to be available.

  The question remaining is: Which level of offline mode will we support? It
  seems reasonable to assume that users will be able to tell when localhost is
  not active (in most cases, localhost should be available, even if the rest of
  the network is not). Therefore, let's concentrate on the state where no

Define extra validations for data types using the "default" value of model attributes. This improves editor support, and it was not available in Pydantic before.

This actually inspired updating parts of Pydantic, to support the same validation declaration style (all this functionality is now already available in Pydantic).

///

### <a href="https://github.com/hugapi/hug" class="external-link" target="_blank">Hug</a> { #hug }

  - name: Create an issue without template
    url: https://github.com/gradle/gradle/issues/new?template=blank

    /** Default current page number. */
    public static final int DEFAULT_CURRENT_PAGE_NUMBER = 1;

    /**
     * The total number of records available.
     */
    private int allRecordCount;

    /**
     * The total number of pages available.
     */
    private int allPageCount;

    /**
     * Whether a previous page exists.
     */
    private boolean existPrePage;

    /**

For the next examples, you could also use `from starlette.middleware.something import SomethingMiddleware`.

**FastAPI** provides several middlewares in `fastapi.middleware` just as a convenience for you, the developer. But most of the available middlewares come directly from Starlette.

///

## `HTTPSRedirectMiddleware` { #httpsredirectmiddleware }

Enforces that all incoming requests must either be `https` or `wss`.

Each process, or "runtime", applies different constraints to the code that runs in that process.
For example, each process has different supported JVMs and a different set of services available for dependency injection.
While a lot of Gradle source code runs only in the Gradle daemon, not all of it does so.