* first decrementing to zero, and then removing. putIfAbsent or replace could observe the
   * intermediate zero-state. Ways we could deal with this are:
   *
   * - Don't define any of the ConcurrentMap operations. This is the current state of affairs.
   *
   * - Define putIfAbsent and replace as treating zero and absent identically (as currently
   *   implemented below). This is a bit surprising with putIfAbsent, which really becomes
   *   putIfZero.

        if (value <= 0) {
            logger.warn("Invalid max history messages: {}. Using default: 20", value);
            return 20;
        }
        return value;
    }

    /**
     * Gets the current number of active sessions.
     *
     * @return the number of active sessions
     */
    public int getActiveSessionCount() {
        return sessionCache.size();
    }

        });
    }

    /**
     * Sets up search paging data for rendering the related query list.
     *
     * @param data the render data to populate
     * @param form the search form containing current search criteria
     */
    protected void searchPaging(final RenderData data, final SearchForm form) {

        CipherSuite.TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,
        CipherSuite.TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,
      )

    // This is nearly equal to the cipher suites supported in Chrome 72, current as of 2019-02-24.
    // See https://tinyurl.com/okhttp-cipher-suites for availability.
    private val APPROVED_CIPHER_SUITES =
      listOf(
        // TLSv1.3.
        CipherSuite.TLS_AES_128_GCM_SHA256,

    }

    public MojoDescriptor getMojo(String goal) {
        if (getMojos() == null) {
            return null; // no mojo in this POM
        }

        // TODO could we use a map? Maybe if the parent did that for components too, as this is too vulnerable to
        // changes above not being propagated to the map
        for (MojoDescriptor desc : getMojos()) {
            if (goal.equals(desc.getGoal())) {

## Order matters { #order-matters }

When creating *path operations*, you can find situations where you have a fixed path.

Like `/users/me`, let's say that it's to get data about the current user.

And then you can also have a path `/users/{user_id}` to get data about a specific user by some user ID.

        final Suggester suggester = Suggester.builder().build(client, "same-index-test");
        suggester.createIndexIfNothing();

        // Get the current indices
        final GetAliasesResponse aliasResponse = client.admin().indices().prepareGetAliases(suggester.getIndex()).execute().actionGet();

        assertNotNull("Should have search alias", aliasResponse.getAliases());

errors.crud_could_not_find_crud_table = The data {0} is not found.
errors.could_not_find_backup_index=Could not find any backup index.
errors.no_user_for_changing_password=The current password is not correct.
errors.failed_to_change_password=Failed to change your password.
errors.unknown_version_for_upgrade=Unknown version for upgrade.
errors.failed_to_upgrade_from=Failed to upgrade from {0}.

errors.crud_could_not_find_crud_table = The data {0} is not found.
errors.could_not_find_backup_index=Could not find any backup index.
errors.no_user_for_changing_password=The current password is not correct.
errors.failed_to_change_password=Failed to change your password.
errors.unknown_version_for_upgrade=Unknown version for upgrade.
errors.failed_to_upgrade_from=Failed to upgrade from {0}.

        String testField = "field999";

        // Warm up
        for (int i = 0; i < 100; i++) {
            queryFieldConfig.isSortField(testField);
        }

        // Measure Set-based lookup (current implementation)
        long setStartTime = System.nanoTime();
        for (int i = 0; i < 10000; i++) {
            queryFieldConfig.isSortField(testField);
        }