call to `chain.proceed(request)` is a critical part of each interceptor’s implementation. 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...

		"Total number of bytes failed at least once to replicate in the last hour on a bucket",
		bucketL, targetArnL)
	bucketReplLastHrFailedCountMD = NewGaugeMD(bucketReplLastHrFailedCount,
		"Total number of objects which failed replication in the last hour on a bucket",
		bucketL, targetArnL)
	bucketReplLastMinFailedBytesMD = NewGaugeMD(bucketReplLastMinFailedBytes,
		"Total number of bytes failed at least once to replicate in the last full minute on a bucket",

        // Act
        // Second close call
        handle.close();

        // Assert
        // sendrecv for open is called once
        verify(mockDcerpcHandle, times(1)).sendrecv(any(MsrpcSamrOpenDomain.class));
        // sendrecv for close is called only once, even if close() is called multiple times
        verify(mockDcerpcHandle, times(1)).sendrecv(any(MsrpcSamrCloseHandle.class));
    }

    @Test

    // lifecycles. The project builder needs to now what default plugin information needs to be
    // merged into POM being built. Once the POM builder has this plugin information, versions can be assigned
    // by the POM builder because they will have to be defined in plugin management. Once this is setComplete then it
    // can be passed back so that the default configuration information can be populated.
    //

    }
  }

  /**
   * Implementing classes should invoke this method once their service has stopped. It will cause
   * the service to transition from {@link State#STARTING} or {@link State#STOPPING} to {@link
   * State#TERMINATED}.
   *
   * @throws IllegalStateException if the service is not one of {@link State#STOPPING}, {@link
   *     State#STARTING}, or {@link State#RUNNING}.
   */

change unified the key-management aspect within MinIO.

The unified KMS-based approach has several advantages:

- Key management is now centralized. There is one way to change or rotate encryption keys.
   There used to be two different mechanisms - one for regular S3 objects and one for IAM data.
- Reduced server startup time. For IAM encryption with the root credentials, MinIO had

			if h.batchSize > 1 && time.Since(lastBatchProcess) < time.Second {
				continue
			}
		}

		// if we have reached the count send at once
		// or we have crossed last second before batch was sent, send at once
		lastBatchProcess = time.Now()

		var retries int
		retryIntvl := h.config.RetryIntvl
		if retryIntvl <= 0 {
			retryIntvl = 3 * time.Second
		}

org.apache.maven.plugins maven-plugin-plugin 0.1 plugin false true addPluginArtifactMet Does nothing. false true false false false true org.apache.maven.plugin.coreit.TestMojo java per-lookup once-per-session descriptor Does nothing. false true false false false true org.apache.maven.plugin.coreit.ItMojo java per-lookup once-per-session org.apache.maven maven-plugin-api jar 2.0 org/apache/maven/plugin/coreit/ItMojo.class package org.apache.maven.plugin.coreit; public synchronized class ItMojo extends org...

org.apache.maven.plugins maven-resources-plugin 0.1 resources false true testResources Does nothing. false true false false false true org.apache.maven.plugin.coreit.TestMojo java per-lookup once-per-session resources Does nothing. false true false false false true org.apache.maven.plugin.coreit.ItMojo java per-lookup once-per-session org.apache.maven maven-plugin-api jar 2.0 org/apache/maven/plugin/coreit/ItMojo.class package org.apache.maven.plugin.coreit; public synchronized class ItMojo extends org....

### Creating the `Settings` only once with `lru_cache` { #creating-the-settings-only-once-with-lru-cache }

Reading a file from disk is normally a costly (slow) operation, so you probably want to do it only once and then reuse the same settings object, instead of reading it for each request.

But every time we do:

```Python
Settings()