The recommended way to file an issue is by running `go bug`.
Otherwise, when filing an issue, make sure to answer these five questions:

1. What version of Go are you using (`go version`)?
2. What operating system and processor architecture are you using?
3. What did you do?
4. What did you expect to see?
5. What did you see instead?

For change proposals, see [Proposing Changes To Go](https://go.dev/s/proposal-process).

        final Builder builder = Settings.builder()
                .putList("http.hosts", hosts)
                .put("processors", fessConfig.getCrawlerHttpProcessors())
                .put("http.heartbeat_interval", fessConfig.getFesenHeartbeatInterval());
        final String username = fessConfig.getFesenUsername();

    NO_URL_IN_QUEUE,
    /** Indicates the start of a crawler thread. */
    START_THREAD,
    /** Indicates the finish of a crawler thread. */
    FINISHED_THREAD,
    /** Indicates no response processor is available. */
    NO_RESPONSE_PROCESSOR,
    /** Indicates no rule is available for processing. */
    NO_RULE,
    /** Indicates a system error occurred. */
    SYSTEM_ERROR

# Helper function to copy a srcjar after moving any source files
# directly under the root to the "maven-style" src/main/java layout
#
# Source files generated by annotation processors appear directly
# under the root of srcjars jars created by bazel, rather than under
# the maven-style src/main/java subdirectory.
#
# Bazel manages annotation generated source as follows: First, it

/**
 * Helper class for managing Fess plugins and artifacts.
 * This class provides functionality to discover, install, and manage various types of plugins
 * including data stores, themes, ingest processors, scripts, web applications, thumbnails, and crawlers.
 */
public class PluginHelper {
    /** Logger instance for this class */
    private static final Logger logger = LogManager.getLogger(PluginHelper.class);

    /**

import org.codelibs.fess.crawler.extractor.Extractor;
import org.codelibs.fess.crawler.extractor.impl.TikaExtractor;
import org.codelibs.fess.crawler.processor.ResponseProcessor;
import org.codelibs.fess.crawler.processor.impl.DefaultResponseProcessor;
import org.codelibs.fess.crawler.rule.Rule;
import org.codelibs.fess.crawler.rule.RuleManager;
import org.codelibs.fess.crawler.serializer.DataSerializer;

     */
    public static QueryFieldConfig getQueryFieldConfig() {
        return getComponent(QUERY_FIELD_CONFIG);
    }

    /**
     * Gets the query processor component.
     * @return The query processor.
     */
    public static QueryProcessor getQueryProcessor() {
        return getComponent(QUERY_PROCESSOR);
    }

    /**
     * Gets the label type helper component.

                new DefaultType(Type.FATJAR, Language.JAVA_FAMILY, "jar", null, true, JavaPathType.CLASSES),
                new DefaultType(
                        Type.PROCESSOR,
                        Language.JAVA_FAMILY,
                        "jar",
                        null,
                        false,
                        JavaPathType.PROCESSOR_CLASSES,

E também depois que a `response` é gerada, antes de retorná-la.

Por exemplo, você pode adicionar um cabeçalho personalizado `X-Process-Time` contendo o tempo em segundos que levou para processar a solicitação e gerar uma resposta:

{* ../../docs_src/middleware/tutorial001_py39.py hl[10,12:13] *}

/// tip | Dica

   * @param callback the LineProcessor to use to handle the lines
   * @return the output of processing the lines
   * @throws IOException if an I/O error occurs
   */
  @CanIgnoreReturnValue // some processors won't return a useful result
  @ParametricNullness
  public static <T extends @Nullable Object> T readLines(
      URL url, Charset charset, LineProcessor<T> callback) throws IOException {