this.session = session;
            return this;
        }

        /**
         * Sets the request trace for this request.
         * The trace is used for debugging and monitoring purposes.
         *
         * @param trace the request trace
         * @return this builder instance
         */
        public ProjectBuilderRequestBuilder trace(RequestTrace trace) {
            this.trace = trace;

        @Option(name = "-s", aliases = "--sessionId", metaVar = "sessionId", usage = "Session ID")
        public String sessionId;

        /** Name for the crawling session for identification purposes. */
        @Option(name = "-n", aliases = "--name", metaVar = "name", usage = "Name")
        public String name;

        /** Comma-separated list of web configuration IDs to crawl. */

This simple-looking method is where all the HTTP work happens, producing a response to satisfy the request. If `chain.proceed(request)` is being called more than once previous response bodies must be closed.

Interceptors can be chained. Suppose you have both a compressing interceptor and a checksumming interceptor: you'll need to decide whether data is compressed and then checksummed, or checksummed and then compressed. OkHttp uses lists to track interceptors, and interceptors are called...

 */
@ExtendWith(MockitoExtension.class)
class NtlmServletTest {

    // A concrete implementation of the abstract NtlmServlet for testing purposes.
    private static class TestNtlmServlet extends NtlmServlet {
        private static final long serialVersionUID = 1L;

        @Override

    @BeforeEach
    void setUp() {
        keys = new KerberosKey[] { kerberosKey };
    }

    /**
     * Creates a byte array representing a Kerberos ticket for testing purposes.
     * @param version Kerberos version
     * @param realm Server realm
     * @param principalName Server principal name
     * @param encType Encryption type
     * @param encryptedData Encrypted data

MinIO needs a persistent volume to store configuration and application data. For testing purposes, you can launch MinIO by simply passing a directory (`/data` in the example below). This directory gets created in the container filesystem at the time of container start. But all the data is lost after container exits.

```sh

        assertNotNull(readings);
        assertEquals(1, readings.size());
        assertEquals("TEST", readings.get(0));
    }

    /**
     * Test implementation of ReadingConverter for testing purposes
     */
    private static class TestReadingConverter implements ReadingConverter {

        private boolean initialized = false;
        private int initCount = 0;
        private boolean japaneseMode = false;

     */
    public abstract String execute();

    /**
     * Returns the execution type identifier for this job.
     * This type is used for classpath construction, configuration, and logging purposes.
     *
     * @return the execution type (e.g., "crawler", "suggest", etc.)
     */
    protected abstract String getExecuteType();

    /**
     * Executes the job with the specified job executor.

### Installing the Chart (toy-setup)

Minimal toy setup for testing purposes can be deployed using:

```bash
helm install --set resources.requests.memory=512Mi --set replicas=1 --set persistence.enabled=false --set mode=standalone --set rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio

import okhttp3.OkHttpClient
import okhttp3.Response
import okhttp3.internal.http2.Header
import okio.Buffer
import okio.BufferedSource
import okio.Source

/** GMT and UTC are equivalent for our purposes. */
@JvmField
internal val UTC: TimeZone = TimeZone.getTimeZone("GMT")!!

internal fun threadFactory(
  name: String,
  daemon: Boolean,
): ThreadFactory =
  ThreadFactory { runnable ->