BuildResult result = runner.buildAndFail();
        assertOutputContains(
            result.getOutput(),
            "Seem like test classes but don't match naming convention:",
            "  * org.elasticsearch.gradle.testkit.LooksLikeATestWithoutNamingConvention1",
            "  * org.elasticsearch.gradle.testkit.LooksLikeATestWithoutNamingConvention2",

    }

    fun allEnabledCipherSuites() =
      apply {
        require(tls) { "no cipher suites for cleartext connections" }
        this.cipherSuites = null
      }

    fun cipherSuites(vararg cipherSuites: CipherSuite): Builder =
      apply {
        require(tls) { "no cipher suites for cleartext connections" }
        val strings = cipherSuites.map { it.javaName }.toTypedArray()
        return cipherSuites(*strings)

plugins:
  - search
  - redirects:
      redirect_maps:
        # Redirect all feature pages to features/*
        'caching.md': 'features/caching.md'
        'calls.md': 'features/calls.md'
        'connections.md': 'features/connections.md'
        'events.md': 'features/events.md'
        'https.md': 'features/events.md'
        'interceptors.md': 'features/interceptors.md'
        'r8_proguard.md': 'features/r8_proguard.md'

                Arguments.of(WinError.ERROR_ACCESS_DENIED, "Access is denied."),
                Arguments.of(WinError.ERROR_REQ_NOT_ACCEP,
                        "No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept."),
                Arguments.of(WinError.ERROR_BAD_PIPE, "The pipe state is invalid."),

  }

  // Node/edge sets are the same, but node/edge connections differ due to edge type.
  @Test
  public void equivalent_directedVsUndirected() {
    graph.putEdge(N1, N2);

    MutableGraph<Integer> g2 = createGraph(oppositeType(edgeType));
    g2.putEdge(N1, N2);

    assertThat(graph).isNotEqualTo(g2);
  }

  // Node/edge sets and node/edge connections are the same, but directedness differs.
  @Test

 *   <li>DEFAULT_MAX_CONNECTION_PER_ROUTE_PROPERTY: Default maximum connections per route.</li>
 *   <li>MAX_TOTAL_CONNECTION_PROPERTY: Maximum total connections.</li>
 *   <li>TIME_TO_LIVE_TIME_UNIT_PROPERTY: Time to live unit for connections.</li>
 *   <li>TIME_TO_LIVE_PROPERTY: Time to live for connections.</li>
 * </ul>
 *
 * @author shinsuke
 */

 */
class AddressPolicy(
  /**
   * How many concurrent calls should be possible to make at any time.
   * The pool will routinely try to pre-emptively open connections to satisfy this minimum.
   * Connections will still be closed if they idle beyond the keep-alive but will be replaced.
   */
  @JvmField val minimumConcurrentCalls: Int = 0,

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE components PUBLIC "-//DBFLUTE//DTD LastaDi 1.0//EN"
	"http://dbflute.org/meta/lastadi10.dtd">
<components>
	<include path="convention.xml" />
	<include path="lastaflute_core.xml"/>
	<include path="fess.xml" />

	<component name="fessSuggest" class="org.codelibs.fess.exec.SuggestCreator"
			   instance="prototype">
	</component>
	<component name="suggestHelper" class="org.codelibs.fess.helper.SuggestHelper">

        private final List<HttpURLConnection> connections = new ArrayList<>();
        private int currentIndex = 0;

        void addConnection(HttpURLConnection conn) {
            connections.add(conn);
        }

        @Override
        protected URLConnection openConnection(URL u) throws IOException {
            if (currentIndex < connections.size()) {
                return connections.get(currentIndex++);

_2016-01-01_

 *  Fix: Don't do a health check on newly-created connections. This is
    unnecessary work that could put the client in an inconsistent state if the
    health check fails.


## Version 2.7.0

_2015-12-13_

 *  **Rewritten connection management.** Previously OkHttp's connection pool
    managed both idle and active connections for HTTP/2, but only idle
    connections for HTTP/1.x. With this update the connection pool manages both