}

// BaseOptions represents common options for all Storage API calls
type BaseOptions struct{}

// RenameOptions represents rename API options, currently its same as BaseOptions
type RenameOptions struct {
	BaseOptions
}

// DiskInfoOptions options for requesting custom results.
type DiskInfoOptions struct {
	DiskID  string `msg:"id"`
	Metrics bool   `msg:"m"`

func (s *Site) Update(n Site) {
	siteLK.Lock()
	s.name = n.name
	s.region = n.region
	siteLK.Unlock()
}

// Name returns currently configured site name
func (s *Site) Name() string {
	siteLK.RLock()
	defer siteLK.RUnlock()

	return s.name
}

// Region returns currently configured site region
func (s *Site) Region() string {
	siteLK.RLock()
	defer siteLK.RUnlock()

	return s.region
}

mode, i.e. standalone or distributed or gateway (nas) ## Distributed MinIO ref: https://docs.minio.io/docs/distributed-minio-quickstart-guide ## NAS Gateway MinIO ref: https://docs.min.io/docs/minio-gateway-for-nas.html mode: distributed ## NOTE: currently only "nas" gateway is supported. ## Additional labels to include with deployment or statefulset additionalLabels: [] ## Additional annotations to include with deployment or statefulset additionalAnnotation: [] ## Additional arguments to pass to minio...

The build of Gradle enables the configuration cache by default as a dogfooding experiment.

Most tasks that are used to build Gradle support the configuration cache, but some don't. For example, building the documentation currently requires you to disable the configuration cache.

To disable the configuration cache, run the build with `--no-configuration-cache`.

Tasks known to have problems are listed in the build logic. You can find this list at:

mode, i.e. standalone or distributed or gateway (nas) ## Distributed MinIO ref: https://docs.minio.io/docs/distributed-minio-quickstart-guide ## NAS Gateway MinIO ref: https://docs.min.io/docs/minio-gateway-for-nas.html mode: distributed ## NOTE: currently only "nas" gateway is supported. ## Additional labels to include with deployment or statefulset additionalLabels: [] ## Additional annotations to include with deployment or statefulset additionalAnnotation: [] ## Additional arguments to pass to minio...

mode, i.e. standalone or distributed or gateway (nas) ## Distributed MinIO ref: https://docs.minio.io/docs/distributed-minio-quickstart-guide ## NAS Gateway MinIO ref: https://docs.min.io/docs/minio-gateway-for-nas.html mode: distributed ## NOTE: currently only "nas" gateway is supported. ## Additional labels to include with deployment or statefulset additionalLabels: [] ## Additional annotations to include with deployment or statefulset additionalAnnotation: [] ## Additional arguments to pass to minio...

mode, i.e. standalone or distributed or gateway (nas) ## Distributed MinIO ref: https://docs.minio.io/docs/distributed-minio-quickstart-guide ## NAS Gateway MinIO ref: https://docs.min.io/docs/minio-gateway-for-nas.html mode: distributed ## NOTE: currently only "nas" gateway is supported. ## Additional labels to include with deployment or statefulset additionalLabels: [] ## Additional annotations to include with deployment or statefulset additionalAnnotation: [] ## Additional arguments to pass to minio...

    /** Thread name for data store crawling process. */
    private static final String DATA_CRAWLING_PROCESS = "DataStoreCrawler";

    /** Atomic flag indicating whether the crawler is currently running. */
    private static AtomicBoolean running = new AtomicBoolean(false);

    /** Thread-safe queue for collecting error messages during crawling operations. */

 *
 * <p><b>For users targeting Android API level 24 or higher:</b> This class will eventually
 * implement {@code BiPredicate<T, T>} (as it does in the main Guava artifact), but we currently
 * target a lower API level. In the meantime, if you have support for method references you can use
 * an equivalence as a bi-predicate like this: {@code myEquivalence::equivalent}.
 *
 * @author Bob Lee
 * @author Ben Yu

   * implementation; otherwise refreshes will be performed during unrelated cache read and write
   * operations.
   *
   * <p>Currently automatic refreshes are performed when the first stale request for an entry
   * occurs. The request triggering refresh will make a synchronous call to {@link
   * CacheLoader#reload}