A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Environment (please complete the following information):**
 - OS: [e.g. Windows 10]
 - Version [e.g. 3.5.0]

**Additional context**

            "Not enough storage is available to process this command.", "The media is write protected.", "The device is not ready.",
            "A device attached to the system is not functioning.", "A device attached to the system is not functioning.",
            "The process cannot access the file because it is being used by another process.",
            "The process cannot access the file because it is being used by another process.",

            "Not enough storage is available to process this command.", "The media is write protected.", "The device is not ready.",
            "A device attached to the system is not functioning.", "A device attached to the system is not functioning.",
            "The process cannot access the file because it is being used by another process.",
            "The process cannot access the file because it is being used by another process.",

---
name: Bug report
about: A reproducible problem
title: ''
labels: bug
assignees: ''

---

Good bug reports include a failing test! Writing a test helps you to isolate and describe the problem, and it helps us to fix it fast. Bug reports without a failing test or reproduction steps are likely to be closed.

Here’s an example test to get you started.

        });
        try {
            badWordService.store(entity);
            suggestHelper.addBadWord(entity.getSuggestWord(), false);
        } catch (final Exception e) {
            logger.warn("Failed to process a request.", e);
            throwValidationErrorApi(messages -> messages.addErrorsCrudFailedToCreateCrudTable(GLOBAL, buildThrowableMessage(e)));
        }

    }

    @Override
    public Optional<Long> sizeIfKnown() {
      if (!(sources instanceof Collection)) {
        // Infinite Iterables can cause problems here. Of course, it's true that most of the other
        // methods on this class also have potential problems with infinite  Iterables. But unlike
        // those, this method can cause issues even if the user is dealing with a (finite) slice()

A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Environment (please complete the following information):**
 - OS: [e.g. Windows 10]
 - Version [e.g. 13.5.0]

**Additional context**

 * This class provides methods to set and get various parameters related to the crawling process.
 *
 * <p>This class is final and cannot be instantiated.</p>
 *
 * <p>The following parameters are managed:</p>
 * <ul>
 *   <li>{@link UrlQueue} - The queue of URLs to be crawled.</li>
 *   <li>{@link CrawlerContext} - The context of the current crawling process.</li>
 *   <li>{@link UrlQueueService} - The service for managing the URL queue.</li>

        scheduledJobService.getScheduledJob(id).ifPresent(entity -> {
            try {
                entity.stop();
            } catch (final Exception e) {
                logger.warn("Failed to process a request.", e);
                throwValidationErrorApi(messages -> {
                    messages.addErrorsFailedToStopJob(GLOBAL, entity.getName());
                });
            }
        }).orElse(() -> {

  }

  /**
   * This test creates a long random sequence of inputs, then a lot of differently configured sinks
   * process it; all should produce the same answer, the only difference should be the number of
   * process()/processRemaining() invocations, due to alignment.
   */
  @AndroidIncompatible // slow. TODO(cpovirk): Maybe just reduce iterations under Android.