* typically set by Maven itself and flagged as readOnly=true or by users via maven-system.properties files.
         * System properties are initialized before the build starts and are available throughout the entire Maven
         * execution. They are used for core Maven functionality that needs to be established at startup.
         */
        SYSTEM_PROPERTIES,
        /**

          <type>String</type>
          <defaultValue><![CDATA[]]></defaultValue>
          <description><![CDATA[If specified, identifies this phase as a dynamic phase to decorate the specified phase id, e.g. {@code after} or {@code before}.]]></description>
        </field>
        <field xml.attribute="true">
          <name>priority</name>
          <required>false</required>
          <version>2.0.0+</version>
          <type>int</type>

}
+-----+

* Logger Name

 Logger name is basically the classical fully qualified class name: it's not visible by default, but can be activated (see {{{/maven-logging.html}user documentation}}).

 Notice that before Maven 3.1.0, with logger created by Maven, some code used to pass logger from class to class because it could not create a new logger:

 * the fact that the problem reporter has/should not have information about the calling context and hence cannot provide
 * an expressive source hint for the model problem. Instead, the source hint is configured by the model builder before
 * it delegates to other components that potentially encounter problems. Then, the problem reporter can focus on
 * providing a simple error message, leaving the donkey work of creating a nice model problem to this component.
 *

También podrías usar `from starlette.requests import Request`.

**FastAPI** lo proporciona como una conveniencia para ti, el desarrollador. Pero viene directamente de Starlette.

///

### Antes y después de la `response` { #before-and-after-the-response }

Puedes añadir código que se ejecute con la `request`, antes de que cualquier *path operation* la reciba.

Y también después de que se genere la `response`, antes de devolverla.

{* ../../docs_src/async_tests/app_a_py310/test_main.py hl[7] *}

/// tip

Note that the test function is now `async def` instead of just `def` as before when using the `TestClient`.

///

Then we can create an `AsyncClient` with the app, and send async requests to it, using `await`.

{* ../../docs_src/async_tests/app_a_py310/test_main.py hl[9:12] *}

import java.util.Map;
import java.util.regex.Pattern;

/**
 * A wrapper class for CrawlerClientFactory that delegates operations to an underlying factory instance.
 * This wrapper allows for parameter management and initialization before delegating to the wrapped factory.
 *
 * The wrapper maintains its own parameter map which can be initialized separately from the wrapped factory,
 * and provides access to the wrapped factory instance through getParent().
 *

        // Should return false for any field, not throw exception
        assertFalse(queryFieldConfig.isFacetField("anyfield"));
        assertFalse(queryFieldConfig.isFacetField("category"));
        // Blank check happens before Set lookup
        assertFalse(queryFieldConfig.isFacetField(""));
    }

    /**
     * Test that isSortField correctly handles null sortFieldSet.
     */
    @Test

                            // Select an appropriate available version from the (now restricted) range
                            // Note this version was selected before to get the appropriate POM
                            // But it was reset by the call to setVersionRange on restricting the version
                            ResolutionNode[] resetNodes = {previous, node};

    happened enough then eventually the connection would stall.

 *  Fix: Acknowledge and apply inbound HTTP/2 settings atomically. Previously we had a race where we
    could use new flow control capacity before acknowledging it, causing strict HTTP/2 servers to
    fail the call.

 *  Fix: Recover gracefully when a coalesced connection immediately goes unhealthy.

## Version 3.14.2

_2019-05-19_