protected CrawlingInfoService crawlingInfoService;

    /**
     * Adds an error message to the error queue for later processing.
     * This method is thread-safe and can be called from multiple crawler threads.
     *
     * @param msg the error message to add; ignored if null or blank
     */
    public static void addError(final String msg) {
        if (StringUtil.isNotBlank(msg)) {
            errors.offer(msg);

    latch = new CountDownLatch(1);
    future = createListenableFuture(Boolean.TRUE, null, latch);
  }

  @Override
  protected void tearDown() throws Exception {

    // Make sure we have no waiting threads.
    latch.countDown();
  }

  /** Constructs a listenable future with a value available after the latch has counted down. */
  protected abstract <V> ListenableFuture<V> createListenableFuture(

     * exception, and wrongly believes that its exception is new (leading it to logging it when it
     * shouldn't)
     *
     * Our solution is for threads to CAS seenExceptionsField from null to a Set populated with _the
     * initial exception_, no matter which thread does the work. This ensures that

   * {@linkplain Thread#getContextClassLoader() context class loader}. In simple environments, the
   * context class loader will find resources from the class path. In environments where different
   * threads can have different class loaders, for example app servers, the context class loader
   * will typically have been set to an appropriate loader for the current thread.
   *

 *  New: Support [JPMS]. We replaced our `Automatic-Module-Name` metadata with proper
    `module-info.java` files.

 *  Fix: Recover gracefully when worker threads are interrupted. When we introduced fast fallback in
    OkHttp 5.0, we started using background threads while connecting. Sadly that code didn't handle
    interruptions well. This is now fixed.

 *  Upgrade: [Kotlin 2.2.20][kotlin_2_2_20].

        log(buf);
    }

    /**
     * Increments the thread reference count for the specified crawler object.
     * Used when the same object is being processed on multiple threads.
     *
     * @param keyObj the crawler object running on an additional thread
     */
    public void runOnThread(final Object keyObj) {
        getCacheKey(keyObj).ifPresent(key -> {
            try {

      return inheritableThreadLocals;
    } catch (Throwable t) {
      logger.log(
          Level.INFO,
          "Couldn't access Thread.inheritableThreadLocals. Reference finalizer threads will "
              + "inherit thread local values.");
      return null;
    }
  }

  private static @Nullable Constructor<Thread> getBigThreadConstructor() {
    try {

    /** Configuration ID */
    public String id;

    /** Configuration name */
    public String name;

    /** File system paths to crawl */
    public String paths;

    /** Number of threads for crawling */
    public String numOfThread;

    /** Interval time between crawling operations */
    public String intervalTime;

    /** Boost value for search ranking */
    public String boost;

    /**
     * The mime type.
     */
    public String mimeType = "application/datastore";

    /**
     * The flag to check if the data store is alive.
     * Volatile to ensure visibility across threads.
     */
    protected volatile boolean alive = true;

    /**
     * Default constructor.
     */
    public AbstractDataStore() {
        // nothing
    }

    /**

   * the {@code shutdownNow} method. First, "best-effort" with regards to canceling running tasks is
   * implemented as "no-effort". No interrupts or other attempts are made to stop threads executing
   * tasks. Second, the returned list will always be empty, as any submitted task is considered to
   * have started execution. This applies also to tasks given to {@code invokeAll} or {@code