plugins {
  kotlin("jvm")
  id("com.gradleup.shadow")
}

tasks.compileJava {
  options.isWarnings = false
}

tasks.jar {
  manifest {
    attributes("Main-Class" to "okhttp3.sample.SampleServer")
  }
}

dependencies {
  implementation(projects.okhttp)
  implementation(projects.mockwebserver)
}

tasks.shadowJar {
  mergeServiceFiles()

                return 0;
            }
        };

        // Callableタスクを複数生成
        final List<Callable<Integer>> tasks = new ArrayList<Callable<Integer>>();
        for (int i = 0; i < numTasks; i++) {
            tasks.add(testCallable);
        }

        // 時間取得
        final long time = System.nanoTime();

        // Callableタスク(複数)を実行する

                display = ParameterDisplay.PROMPT,
                allowEmpty = false,
                description = "The test task you want to run",
            )
            text(
                testNameParameterName,
                """org.gradle.api.tasks.CachedTaskExecutionIntegrationTest.outputs*are*correctly*loaded*from*cache""",
                display = ParameterDisplay.PROMPT,

    end
    operation ->> client: Return response to client
    Note over client,operation: Response is already sent, can't change it anymore
    opt Tasks
        operation -->> tasks: Send background tasks
    end
    opt Raise other exception
        tasks -->> dep: Raise other exception
    end
    Note over dep: After yield
    opt Handle other exception

                    tasks = "clean :distributions-full:install"
                    gradleParams =
                        "-Pgradle_installPath=dogfood-first -PignoreIncomingBuildReceipt=true -PbuildTimestamp=$dogfoodTimestamp1 $defaultParameters"
                }

                localGradle {
                    name = "BUILD_WITH_BUILT_GRADLE"
                    tasks = "clean :distributions-full:install"

# Background Tasks - `BackgroundTasks`

You can declare a parameter in a *path operation function* or dependency function with the type `BackgroundTasks`, and then you can use it to schedule the execution of background tasks after the response is sent.

You can import it directly from `fastapi`:

```python
from fastapi import BackgroundTasks
```

* Then it returns the **response**.

/// note | Technical Details

If you have dependencies with `yield`, the exit code will run *after* the middleware.

If there were any background tasks (covered in the [Background Tasks](background-tasks.md){.internal-link target=_blank} section, you will see it later), they will run *after* all the middleware.

///

## Create a middleware { #create-a-middleware }

├── Smb2LeaseKey.java            - 16-byte lease key management
├── Smb2LeaseState.java          - Lease state flags (R, H, W)
└── LeaseManager.java            - Central lease management
```

#### 1.2 Implementation Tasks
- [ ] Define lease state constants (SMB2_LEASE_READ, SMB2_LEASE_HANDLE, SMB2_LEASE_WRITE)
- [ ] Implement lease key generation and management
- [ ] Add lease context to Create request/response

Directory for log files of DBFlute tasks

If your execution of DBFlute task fails,

## Team

There's a team of people that help manage and maintain the project. 😎

They have different levels of permissions and [specific instructions](./management-tasks.md){.internal-link target=_blank}.

Some of the tasks they can perform include:

* Adding labels to PRs.
* Editing PR titles.
* Adding commits on top of PRs to tweak them.
* Mark answers in GitHub Discussions questions, etc.