},
        "german_keywords": {
          "type":       "keyword_marker",

errors.app.db.already.deleted = Es wurde möglicherweise von einem anderen Prozess gelöscht. Bitte versuchen Sie den Vorgang erneut.
errors.app.db.already.updated = Es wurde möglicherweise von einem anderen Prozess aktualisiert. Bitte versuchen Sie den Vorgang erneut.
errors.app.db.already.exists = Die Daten sind bereits vorhanden. Bitte versuchen Sie den Vorgang erneut.

     *
     * @param searchEngineClient the search engine client to use for deletion
     * @param docList the list of new documents to check against
     * @return the number of old documents that were deleted
     */
    protected long deleteOldDocuments(final SearchEngineClient searchEngineClient, final DocList docList) {
        final FessConfig fessConfig = ComponentUtil.getFessConfig();

### Motivation

This library makes it easy to test that your app Does The Right Thing when it
makes HTTP and HTTPS calls. It lets you specify which responses to return and
then verify that requests were made as expected.

Because it exercises your full HTTP stack, you can be confident that you're
testing everything. You can even copy & paste HTTP responses from your real web

        String result = purgeLogJob.execute();

        // Assert all services were called
        assertTrue(deleteCrawlingInfoCalled[0]);
        assertTrue(deleteSearchLogCalled[0]);
        assertTrue(deleteJobLogCalled[0]);
        assertTrue(deleteUserInfoCalled[0]);
        assertTrue(updateJobLogStatusCalled[0]);

        // Assert correct parameters were passed - verify that time passed is greater than 0

 * the keys in the order they were first added to the multimap. Similarly, {@code get}, {@code
 * removeAll}, and {@code replaceValues} return collections that iterate through the values in the
 * order they were added. The collections generated by {@code entries} and {@code values} iterate
 * across the key-value mappings in the order they were added to the multimap.
 *

 * the order they were first added to the multimap. Similarly, {@link #get}, {@link #removeAll}, and
 * {@link #replaceValues} return collections that iterate through the values in the order they were
 * added. The collections generated by {@link #entries()}, {@link #keys()}, and {@link #values}
 * iterate across the key-value mappings in the order they were added to the multimap.
 *

import org.junit.jupiter.api.extension.ExtensionContext
import org.junit.rules.TestRule
import org.junit.runner.Description
import org.junit.runners.model.Statement

/**
 * A log handler that records which log messages were published so that a calling test can make
 * assertions about them.
 */
class TestLogHandler(
  private val logger: Logger,
) : TestRule,
  BeforeEachCallback,
  AfterEachCallback {

        authenticationManager.addChain(chain1);
        authenticationManager.addChain(chain2);
        authenticationManager.addChain(chain3);

        // Verify all chains were added by testing their effect
        User user = createTestUser("testuser");
        authenticationManager.insert(user);

        assertEquals(1, chain1.updateCallCount);
        assertEquals(1, chain2.updateCallCount);

 *
 * <p><b>Warning:</b> Chunks of data that are put into the {@link Hasher} are not delimited. The
 * resulting {@link HashCode} is dependent only on the bytes inserted, and the order in which they
 * were inserted, not how those bytes were chunked into discrete put() operations. For example, the
 * following three expressions all generate colliding hash codes:
 *
 * {@snippet :
 * newHasher().putByte(b1).putByte(b2).putByte(b3).hash()