* Restarts
* **Replication (the number of processes running)**
* Memory
* Previous steps before starting

Up to this point, with all the tutorials in the docs, you have probably been running a **server program**, for example, using the `fastapi` command, that runs Uvicorn, running a **single process**.

                    e.printStackTrace();
                }

                // despite all are back, we need to make sure all the events are processed (are async)
                // this one should block until all processed
                listener.transferSucceeded(new TransferEvent.Builder(session, resource)
                        .setType(TransferEvent.EventType.SUCCEEDED)
                        .build());

     * @return set of projects that have yet to be processed successfully by the build.
     */
    public Set<MavenProject> getUnfinishedProjects() {
        Set<MavenProject> unfinished = new HashSet<>(projectBuilds.getProjects());
        unfinished.removeAll(finishedProjects);
        return unfinished;
    }

    /**
     * @return set of projects that have been successfully processed by the build.
     */

            this.snippet = snippet;
        }

        /**
         * Gets the ViewHelper-processed URL for display.
         *
         * @return the URL link
         */
        public String getUrlLink() {
            return urlLink;
        }

        /**
         * Sets the ViewHelper-processed URL for display.
         *
         * @param urlLink the URL link
         */

      sink.flush()
    }
  }

  /**
   * Tell the peer to stop creating streams and that we last processed `lastGoodStreamId`, or zero
   * if no streams were processed.
   *
   * @param lastGoodStreamId the last stream ID processed, or zero if no streams were processed.
   * @param errorCode reason for closing the connection.
   * @param debugData only valid for HTTP/2; opaque debug data to send.
   */

### Containers with Multiple Processes and Special Cases { #containers-with-multiple-processes-and-special-cases }

Of course, there are **special cases** where you could want to have **a container** with several **Uvicorn worker processes** inside.

In those cases, you can use the `--workers` command line option to set the number of workers that you want to run:

A "middleware" is a function that works with every **request** before it is processed by any specific *path operation*. And also with every **response** before returning it.

* It takes each **request** that comes to your application.
* It can then do something to that **request** or run any needed code.
* Then it passes the **request** to be processed by the rest of the application (by some *path operation*).

## Decision

1. The Gradle distribution will never include a Java runtime.
   Instead, Gradle will leverage Java toolchains for the Daemon and worker processes.
2. The Gradle Daemon, Worker processes, and Tooling API client will continue to support running on different Java versions during a single Gradle invocation.
   The exact versions supported will be determined by the Gradle version.

    @Test
    public void test_execute_success() {
        String result = updateLabelJob.execute();
        assertNotNull(result);
        assertTrue(result.contains("3 documents")); // 3 documents processed
        assertFalse(result.contains("exception"));
    }

    // Test execute() method with query builder
    @Test
    public void test_execute_withQueryBuilder() {

// Progress message payload is an XML document containing information about the progress of a request.
//   - BytesScanned => Number of bytes that have been processed before being uncompressed (if the file is compressed).
//   - BytesProcessed => Number of bytes that have been processed after being uncompressed (if the file is compressed).
//   - BytesReturned => Current number of bytes of records payload data returned by S3.
//