*
 * {@code CacheBuilder} builds caches with any combination of the following features:
 *
 * <ul>
 *   <li>automatic loading of entries into the cache
 *   <li>least-recently-used eviction when a maximum size is exceeded (note that the cache is
 *       divided into segments, each of which does LRU internally)
 *   <li>time-based expiration of entries, measured since last access or last write

common:windows --host_copt=/D_USE_MATH_DEFINES

# Windows has a relatively short command line limit, which TF has begun to hit.
# See https://docs.bazel.build/versions/main/windows.html
common:windows --features=compiler_param_file
common:windows --features=archive_param_file

# Speed Windows compile times. Available in VS 16.4 (we are on 16.11). See
# https://groups.google.com/a/tensorflow.org/d/topic/build/SsW98Eo7l3o/discussion

 *
 * {@code CacheBuilder} builds caches with any combination of the following features:
 *
 * <ul>
 *   <li>automatic loading of entries into the cache
 *   <li>least-recently-used eviction when a maximum size is exceeded (note that the cache is
 *       divided into segments, each of which does LRU internally)
 *   <li>time-based expiration of entries, measured since last access or last write

    - [Other notable changes](#other-notable-changes-10)
- [v1.3.0-beta.2](#v130-beta2)
  - [Downloads](#downloads-11)
  - [Changes since v1.3.0-beta.1](#changes-since-v130-beta1)
    - [Experimental Features](#experimental-features)
    - [Other notable changes](#other-notable-changes-11)
- [v1.3.0-beta.1](#v130-beta1)
  - [Downloads](#downloads-12)
  - [Changes since v1.3.0-alpha.5](#changes-since-v130-alpha5)

 * This executor implements a weave-mode build strategy, where builds are executed phase-by-phase rather than
 * project-by-project.
 *
 * <h2>Key Features:</h2>
 * <ul>
 *   <li>Concurrent execution of compatible build steps across projects</li>
 *   <li>Thread-safety validation for plugins</li>
 *   <li>Support for forked executions and lifecycle phases</li>

 * Futures#transform(ListenableFuture, Function, Executor) Futures.transform}, but you will often
 * find it easier to use a framework. Frameworks automate the process, often adding features like
 * monitoring, debugging, and cancellation. Examples of frameworks include:
 *
 * <ul>
 *   <li><a href="https://dagger.dev/producers.html">Dagger Producers</a>
 * </ul>
 *

import com.google.common.collect.testing.ListTestSuiteBuilder;
import com.google.common.collect.testing.TestStringListGenerator;
import com.google.common.collect.testing.features.CollectionFeature;
import com.google.common.collect.testing.features.CollectionSize;
import com.google.common.collect.testing.features.ListFeature;
import com.google.common.primitives.Ints;
import com.google.common.testing.NullPointerTester;
import java.util.ArrayList;

        "@platforms//cpu:x86_64",
    ],
    visibility = ["//visibility:public"],
)

# Features that are default ON are handled differently below.
#
config_setting(
    name = "no_gcp_support",
    define_values = {"no_gcp_support": "true"},
    visibility = ["//visibility:public"],
)

# Experimental features
config_setting(
    name = "stackdriver_support",
    define_values = {"stackdriver_support": "true"},

        assertTrue(readmeFile.exists(), "File in public share should be accessible");
        assertTrue(readmeFile.canRead(), "File in public share should be readable");
    }

    // ========== Advanced Features ==========

    @Test
    void testLargeFileOperations() throws Exception {
        SmbFile file = new SmbFile(baseUrl + "shared/largefile.bin", context);

        // Create a smaller test file (1KB instead of 1MB)

		class="org.codelibs.fess.crawler.extractor.impl.HtmlExtractor">
		<property name="featureMap">
			<component class="java.util.LinkedHashMap">
				<postConstruct name="put">
					<arg>"http://xml.org/sax/features/namespaces"</arg>
					<arg>"false"</arg>
				</postConstruct>
			</component>
		</property>
		<property name="propertyMap">
			<component class="java.util.LinkedHashMap">
			</component>
		</property>