assertThat(response!!.networkResponse).isNull()
    }

  /** Asserts that the current response didn't use the cache.  */
  fun assertNoCacheResponse() =
    apply {
      assertThat(response!!.cacheResponse).isNull()
    }

  /**
   * Asserts that the current response used the cache and returns the cache response.
   */
  fun cacheResponse(): RecordedResponse {
    val cacheResponse = response!!.cacheResponse!!

```Dockerfile
RUN pip install --no-cache-dir --upgrade -r /code/requirements.txt
```

Die Datei mit den Paketanforderungen wird sich **nicht häufig ändern**. Wenn Docker also nur diese Datei kopiert, kann es für diesen Schritt **den Cache verwenden**.

  grep -v "twine" $REQUIREMENTS > requirements_without_twine.txt
  REQUIREMENTS=requirements_without_twine.txt
fi

# Disable the cache dir to save image space, and install packages

    }

    /**
     * Benchmark that tests cache benefits by repeatedly setting properties on the same class.
     * This better demonstrates the caching improvements.
     */
    @Benchmark
    public void benchmarkOriginalHelperRepeatedOperations() throws Exception {
        // Test cache benefits by using same class multiple times
        for (int i = 0; i < 10; i++) {

        build/errorLogs/** => $HIDDEN_ARTIFACT_DESTINATION/errorLogs
        artifact-cache-metrics => artifact-cache-metrics
        artifact-cache-report => artifact-cache-report
        build/reports/configuration-cache/**/configuration-cache-report.html
        subprojects/internal-build-reports/build/reports/incubation/all-incubating.html => incubation-reports

import com.fasterxml.jackson.core.JsonProcessingException;
import com.fasterxml.jackson.databind.ObjectMapper;
import com.google.common.base.CaseFormat;
import com.google.common.cache.CacheBuilder;
import com.google.common.cache.CacheLoader;
import com.google.common.cache.LoadingCache;

import jakarta.annotation.PostConstruct;

/**
 * Helper class for managing search logs.
 */
public class SearchLogHelper {

    }

    // Test for cache method
    @Test
    void testCache_DfsDisabled() {
        when(mockConfig.isDfsDisabled()).thenReturn(true);
        DfsReferralData mockReferralData = mock(DfsReferralData.class);
        assertDoesNotThrow(() -> dfsResolver.cache(mockContext, "\\\\anyServer\\anyShare\\anyPath", mockReferralData));
    }

    @Test

```Dockerfile
RUN pip install --no-cache-dir --upgrade -r /code/requirements.txt
```

El archivo con los requisitos de los paquetes **no cambiará con frecuencia**. Así que, al copiar solo ese archivo, Docker podrá **usar la caché** para ese paso.

internal fun addHeaderLenient(
  builder: Headers.Builder,
  name: String,
  value: String,
): Headers.Builder = builder.addLenient(name, value)

internal fun cacheGet(
  cache: Cache,
  request: Request,
): Response? = cache.get(request)

internal fun applyConnectionSpec(
  connectionSpec: ConnectionSpec,
  sslSocket: SSLSocket,
  isFallback: Boolean,
) = connectionSpec.apply(sslSocket, isFallback)

// reasons. Note that ZFS is effectively the default filesystem on illumos
// systems.
//
// One benefit of using DirectIO on Linux is that the page cache will not be
// polluted with single-access data. The ZFS read cache (ARC) is scan-resistant
// so there is no risk of polluting the entire cache with data accessed once.
// Another goal of DirectIO is to minimize the mutation of data by the kernel