///

### [Requests](https://requests.readthedocs.io) { #requests }

**FastAPI** n'est pas réellement une alternative à **Requests**. Leur cadre est très différent.

Il serait en fait plus courant d'utiliser Requests _à l'intérieur_ d'une application FastAPI.

Mais quand même, FastAPI s'est inspiré de Requests.

    }

    /**
     * Check whether any of the requested optional projects were not activated or deactivated.
     * @param request the {@link MavenExecutionRequest}.
     * @param session the {@link MavenSession}.
     */
    private void validateOptionalProjects(MavenExecutionRequest request, MavenSession session) {
        final ProjectActivation projectActivation = request.getProjectActivation();

		}
	}

	if globalIsDistErasure {
		logger.Info("Configured max API requests per node based on available memory: %d", apiRequestsMaxPerNode)
	}

	if cap(t.requestsPool) != apiRequestsMaxPerNode {
		// Only replace if needed.
		// Existing requests will use the previous limit,
		// but new requests will use the new limit.
		// There will be a short overlap window,
		// but this shouldn't last long.

        } catch (CIFSException e) {
            throw SmbException.wrap(e);
        }
    }

    /**
     * Request directory lease for the given directory
     *
     * @param smbFile the directory to request lease for
     * @param requestedState requested lease state
     * @param scope cache scope
     * @return lease key or null if not supported
     * @throws SmbException if an error occurs

- https://gitbox.apache.org/repos/asf/lucene-solr.git

## GitHub forks?

If you are using GitHub, make a clone of the corresponding repository
mirror and create your pull requests against the main branch:

- Lucene: <https://github.com/apache/lucene>

## Revise Pull Requests { #review-pull-requests }

Você pode me ajudar revisando pull requests de outras pessoas.

Novamente, por favor tente ao máximo ser gentil. 🤗

---

Veja o que ter em mente e como revisar um pull request:

### Entenda o problema { #understand-the-problem }

# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms
# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema
name: Bugs
description: The go command, standard library, or anything else
title: "import/path: issue title"

body:
  - type: markdown
    attributes:

 * </ul>
 *
 * @param <REQ> the type of Request that produced this result, ensuring type-safe
 *              access to the original request parameters
 *
 * @see Request
 * @since 4.0.0
 */
@Experimental
@Immutable
public interface Result<REQ extends Request<?>> {

    /**
     * Returns the request that produced this result.
     *
     * @return the originating request instance, never {@code null}
     */

Al desplegar aplicaciones probablemente querrás tener algo de **replicación de procesos** para aprovechar **múltiples núcleos** y poder manejar más requests.

Como viste en el capítulo anterior sobre [Conceptos de Despliegue](concepts.md), hay múltiples estrategias que puedes usar.

/// tip | Совет

Сам обратный вызов — это всего лишь HTTP-запрос.

Реализуя обратный вызов, вы можете использовать, например, [HTTPX](https://www.python-httpx.org) или [Requests](https://requests.readthedocs.io/).

///

## Напишите код документации обратного вызова { #write-the-callback-documentation-code }