labels.scheduledjob_scriptData=Script
labels.scheduledjob_jobLogging=Logging
labels.scheduledjob_crawler=Trabalho do rastreador
labels.scheduledjob_running=Em execução
labels.scheduledjob_active=Ativo
labels.scheduledjob_nojob=Inativo
labels.scheduledjob_button_start=Iniciar agora
labels.scheduledjob_button_stop=Parar
labels.joblog_button_back=Voltar
labels.joblog_button_delete=Excluir
labels.joblog_configuration=Log de trabalho

{
  "detail": "Not authenticated"
}
```

### Usuario inactivo { #inactive-user }

Ahora prueba con un usuario inactivo, autentícate con:

Usuario: `alice`

Contraseña: `secret2`

Y trata de usar la operación `GET` con la path `/users/me`.

Obtendrás un error de "Usuario inactivo", como:

```JSON
{
  "detail": "Inactive user"
}
```

## Recapitulación { #recap }

This directory contains JLine native libraries extracted from JLine JAR.

You can add your own build for platforms not natively supported by JLine.
See here [1] on how to compile for your platform and here [2] how libraries
follow JLine's directory and filename conventions.

[1] https://github.com/jline/jline3/tree/master/native

  }
}

/**
 * Subset of the elemental2 IThenable interface without the single-parameter overload, which allows
 * us to implement it using a default implementation in J2cl ListenableFuture.
 */
@JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "IThenable")
interface IThenable<T extends @Nullable Object> {
  <V extends @Nullable Object> IThenable<V> then(

}
```

### Inaktiver Benutzer { #inactive-user }

Versuchen Sie es nun mit einem inaktiven Benutzer und authentisieren Sie sich mit:

Benutzer: `alice`.

Passwort: `secret2`.

Und versuchen Sie, die Operation `GET` mit dem Pfad `/users/me` zu verwenden.

Sie erhalten die Fehlermeldung „Inactive user“:

```JSON
{
  "detail": "Inactive user"
}
```

## Zusammenfassung { #recap }

cpovirk <******@****.***> 1685135561 -0700

Yuri Schimke <******@****.***> 1735306796 +0200

Y para comunicarte usando WebSockets con tu backend probablemente usarías las utilidades de tu frontend.

O podrías tener una aplicación móvil nativa que se comunica con tu backend de WebSocket directamente, en código nativo.

O podrías tener alguna otra forma de comunicarte con el endpoint de WebSocket.

---

        <include>*.conf</include>
        <include>*.java</include>
      </includes>
      <lineEnding>dos</lineEnding>
    </fileSet>
    <fileSet>
      <directory>target/dependency/org/jline/nativ</directory>
      <outputDirectory>lib/jline-native</outputDirectory>
      <includes>
        <include>**/*.so</include>
        <include>**/*.jnilib</include>
        <include>**/*.dll</include>
      </includes>
    </fileSet>
	<fileSet>

        <executions>
          <execution>
            <id>unpack-jline-native</id>
            <goals>
              <goal>unpack-dependencies</goal>
            </goals>
            <configuration>
              <includeArtifactIds>jline-native</includeArtifactIds>
              <includes>org/jline/nativ/**</includes>
            </configuration>
          </execution>
        </executions>