protected long executeTime;

    /** Total number of processed documents */
    protected long documentSize;

    /** Maximum number of indexer errors allowed */
    protected int maxIndexerErrorCount = 0;

    /** Maximum number of general errors allowed before termination */
    protected int maxErrorCount = 2;

    /** List of finished crawler session IDs for cleanup */

- github.com/docker/docker: [v20.10.18+incompatible → v20.10.21+incompatible](https://github.com/docker/docker/compare/v20.10.18...v20.10.21)
- github.com/go-errors/errors: [v1.0.1 → v1.4.2](https://github.com/go-errors/errors/compare/v1.0.1...v1.4.2)
- github.com/go-openapi/jsonpointer: [v0.19.5 → v0.19.6](https://github.com/go-openapi/jsonpointer/compare/v0.19.5...v0.19.6)

    private int currentPageNumber;

    /** ID of the failure URL record. */
    public String id;

    /** Name of the thread that encountered the failure. */
    public String threadName;

    /** Number of errors encountered for this URL. */
    public String errorCount;

    /** Last time this URL was accessed. */
    public String lastAccessTime;

    /**
     * Clears all pager data and resets to default values.

    }

    /**
     * Creates a synonym item from the provided form data with validation.
     *
     * @param form the create form containing synonym data
     * @param hook the validation error hook for handling errors
     * @return OptionalEntity containing the created synonym item or empty if creation failed
     */
    protected OptionalEntity<SynonymItem> createSynonymItem(final CreateForm form, final VaErrorHook hook) {
        try {

                } catch (Exception e) {
                    log.debug("Error in async notification monitoring for {}: {}", registrationId, e.getMessage());

                    // Exponential backoff on errors: max 30 seconds, based on consecutive failures
                    try {
                        int failures = Math.min(registration.getHeartbeatFailures(), MAX_FAILURE_LIMIT);

 * </p>
 *
 * <p>
 * It handles potential exceptions during file creation and storage, throwing
 * {@link org.codelibs.fess.crawler.exception.CrawlerSystemException} in case of errors.
 * </p>
 *
 * <p>
 * The {@link #storeData(ResponseData, ResultData)} method is the main entry point for storing
 * the content of a crawled resource. The {@link #getData(AccessResultData)} method retrieves

     * can propagate through many layers of AbstractTransformFuture up to the root call to set().
     *
     * https://github.com/google/guava/issues/2254
     *
     * Other kinds of Errors are possible:
     *
     * - OutOfMemoryError from allocations in setFuture(): The calculus here is similar to
     * StackOverflowError: We can't reliably call setException(error).
     *

    }

    @Test
    public void testMultipleSecureWipes() {
        authenticator = new NtlmPasswordAuthenticator("DOMAIN", "username", "password");

        // Multiple wipes should not cause errors
        authenticator.secureWipePassword();
        authenticator.secureWipePassword();
        authenticator.secureWipePassword();

        context.put("username", "******@****.***");

        logger.logEvent(EventType.AUTHENTICATION_SUCCESS, Severity.INFO, "Login attempt", context);

        // The test verifies that the logger runs without errors when masking is enabled
        Map<EventType, Long> stats = logger.getStatistics();
        assertEquals(Long.valueOf(1), stats.get(EventType.AUTHENTICATION_SUCCESS), "Should have 1 authentication event");
    }

    } catch (Exception e) { // sneaky checked exception
      // Log it and keep going -- bad runnable and/or executor. Don't punish the other runnables if
      // we're given a bad one. We only catch Exception because we want Errors to propagate up.
      log.get()
          .log(
              Level.SEVERE,
              "RuntimeException while executing runnable "
                  + runnable
                  + " with executor "