*/
    public AdminDuplicatehostAction() {
        super();
    }

    /**
     * Role name for duplicate host administration.
     */
    public static final String ROLE = "admin-duplicatehost";

    private static final Logger logger = LogManager.getLogger(AdminDuplicatehostAction.class);

    // ===================================================================================

        // Test with chain containing both Errors and Exceptions
        String message = "SSO login complex error chain";
        IllegalStateException innerException = new IllegalStateException("Bad state");
        AssertionError middleError = new AssertionError("Assertion failed", innerException);
        RuntimeException outerException = new RuntimeException("Wrapper exception", middleError);

    }

    @Test
    public void test_setCrawlerRunning() {
        IntervalControlHelper helper = new IntervalControlHelper();

        // Test default state
        assertTrue(helper.isCrawlerRunning());

        // Test setting to false
        helper.setCrawlerRunning(false);
        assertFalse(helper.isCrawlerRunning());

        // Test setting back to true

    fun addProjectState(projectPath: String, projectBuildDir: Provider<File>, reportOnly: Provider<Boolean>) {
        require(projectPath !in projectStates.keys) { "Project state already added for $projectPath" }
        projectStates[projectPath] = TestFilesCleanupProjectState(projectPath, projectBuildDir, reportOnly)
    }

# Lifespan Events { #lifespan-events }

You can define logic (code) that should be executed before the application **starts up**. This means that this code will be executed **once**, **before** the application **starts receiving requests**.

The same way, you can define logic (code) that should be executed when the application is **shutting down**. In this case, this code will be executed **once**, **after** having handled possibly **many requests**.

    this was confusing.
 *  Fix: Omit the message from MockWebServer's HTTP/2 `:status` header.
 *  Fix: Handle 'Expect: 100 Continue' properly in MockWebServer.


## Version 3.8.1

_2017-06-18_

 *  Fix: Recover gracefully from stale coalesced connections. We had a bug where
    connection coalescing (introduced in OkHttp 3.7.0) and stale connection
    recovery could interact to cause a `NoSuchElementException` crash in the

./mc ls -r --versions myminio/versioned/ >expanded_ns_versions.txt

./mc admin decom start myminio/ http://localhost:9000/tmp/xl/{1...10}/disk{0...1}

count=0
until $(./mc admin decom status myminio/ | grep -q Complete); do
	echo "waiting for decom to finish..."
	count=$((count + 1))
	if [ ${count} -eq 120 ]; then
		./mc cat /tmp/expanded_*.log
	fi
	sleep 1
done

kill $pid_1

 * or implied. See the License for the specific language governing permissions and limitations under
 * the License.
 */

package com.google.common.collect;

import static com.google.common.collect.Internal.toNanosSaturated;
import static java.util.concurrent.TimeUnit.NANOSECONDS;

import com.google.common.annotations.GwtCompatible;
import com.google.common.annotations.GwtIncompatible;

 * or implied. See the License for the specific language governing permissions and limitations under
 * the License.
 */

package com.google.common.util.concurrent;

import static com.google.common.util.concurrent.MoreExecutors.directExecutor;
import static java.util.concurrent.TimeUnit.MILLISECONDS;

import com.google.common.annotations.GwtIncompatible;
import com.google.common.annotations.J2ktIncompatible;

	input       chan *queueItem           // input for workers
	queue       chan *queueItem           // output from workers in order
	err         error                     // global error state, only touched by Reader.Read
	bufferPool  bpool.Pool[[]byte]        // pool of []byte objects for input
	kvDstPool   bpool.Pool[[]jstream.KVS] // pool of []jstream.KVS used for output