verifyNoMoreInteractions(locator);
    }

    // Error path: overlaps may throw a CIFSException per signature
    @Test
    @DisplayName("overlaps throws CIFSException when implementation fails")
    void overlapsThrowsCifsException() throws Exception {
        when(locator.overlaps(any())).thenThrow(new CIFSException("Simulated failure"));

{* ../../docs_src/response_model/tutorial001_01_py310.py hl[16,21] *}

Comme cela se passe côté Rust, la performance sera bien meilleure que si cela était fait avec le Python classique et la classe `JSONResponse`.

## Acessando o corpo da requisição em um manipulador de exceção { #accessing-the-request-body-in-an-exception-handler }

/// tip | Dica

Para resolver esse mesmo problema, é provavelmente muito mais fácil usar o `body` em um manipulador personalizado para `RequestValidationError` ([Tratando Erros](../tutorial/handling-errors.md#use-the-requestvalidationerror-body)).

  </module>

  <!--
    We include snippets that are wrapped in `// tag` and `// end` into the
    docs, stripping the leading spaces. If the context is wider than 76
    characters then it'll need to scroll. This fails the build if it sees
    such snippets.
  -->
  <module name="org.elasticsearch.gradle.internal.checkstyle.SnippetLengthCheck">
    <property name="id" value="SnippetLength" />
    <property name="max" value="76" />

	if crypto.S3.IsRequested(r.Header) || crypto.S3KMS.IsRequested(r.Header) { // If SSE-S3 or SSE-KMS present -> AWS fails with undefined error
		writeErrorResponse(ctx, w, errorCodes.ToAPIErr(ErrBadRequest), r.URL)
		return
	}

	zipPath, object, err := splitZipExtensionPath(object)
	if err != nil {

Ensuite, il 🤖 prendra la première tâche à finir (disons, notre « slow-file » 📝) et continuera à faire avec cette dernière ce qu'il était censé.

Ce « attendre quelque chose d'autre » fait généralement référence à des opérations <abbr title="Input and Output - Entrées et sorties">I/O</abbr> qui sont relativement « lentes » (comparées à la vitesse du processeur et de la mémoire RAM) telles qu'attendre que :

labels.user_given_name=Nome
labels.givenName=Nome (dado)
labels.user_surname=Sobrenome
labels.surame=Sobrenome
labels.user_mail=Endereço de e-mail
labels.mail=Endereço de e-mail
labels.user_employeeNumber=Número do funcionário
labels.employeeNumber=Número do funcionário
labels.user_telephoneNumber=Número de telefone
labels.telephoneNumber=Número de telefone

// Begin constructs a SCRAM client component based on a given hash.Hash
// factory receiver.  This constructor will normalize the username, password
// and authzID via the SASLprep algorithm, as recommended by RFC-5802.  If
// SASLprep fails, the method returns an error.
func (x *XDGSCRAMClient) Begin(userName, password, authzID string) (err error) {
	x.Client, err = x.NewClient(userName, password, authzID)
	if err != nil {
		return err
	}

     * @param username the username of the user performing the operation
     * @param currentTime the current timestamp
     * @return optional entity containing the scheduled job data, or empty if creation fails
     */
    private static OptionalEntity<ScheduledJob> getEntity(final CreateForm form, final String username, final long currentTime) {
        switch (form.crudMode) {
        case CrudMode.CREATE:

   * permit them, as it seems more likely that code would depend on that behavior than on the other.
   * Thus, we say the bug is in add(), which fails to support null.
   */
  @J2ktIncompatible
  @GwtIncompatible // reflection
  public static Method getAddNullSupportedMethod() {
    return getMethod(CollectionAddTester.class, "testAdd_nullSupported");
  }