assertEquals(24, written);
        assertEquals(combinedFlags, SMBUtil.readInt2(buffer, 2));
    }

    @Test
    @DisplayName("Test request state after multiple operations")
    void testRequestStateAfterMultipleOperations() throws Exception {
        // Set initial values
        request.setCloseFlags(0x0001);

        // Change file ID
        byte[] newFileId1 = new byte[16];

public class AdminSchedulerAction extends FessAdminAction {

    /**
     * Default constructor.
     */
    public AdminSchedulerAction() {
        super();
    }

    /** Role name for admin scheduler operations */
    public static final String ROLE = "admin-scheduler";

    private static final Logger logger = LogManager.getLogger(AdminSchedulerAction.class);

public class AdminWebconfigAction extends FessAdminAction {

    /**
     * Default constructor.
     */
    public AdminWebconfigAction() {
        super();
    }

    /** Role name for admin web config operations */
    public static final String ROLE = "admin-webconfig";

    private static final Logger logger = LogManager.getLogger(AdminWebconfigAction.class);

It's optional to use it, but that's where you would put the user's identification, so we are using it here.

JWT might be used for other things apart from identifying a user and allowing them to perform operations directly on your API.

For example, you could identify a "car" or a "blog post".

Then you could add permissions about that entity, like "drive" (for the car) or "edit" (for the blog).

La façon dont vous l'utilisez est très simple. Par exemple, pour faire une requête `GET`, vous devez écrire :

```Python
response = requests.get("http://example.com/some/url")
```

En contrepartie l'API _des opérations de chemin_ de FastAPI pourrait ressembler à ceci :

```Python hl_lines="1"
@app.get("/some/url")
def read_url():
    return {"message": "Hello World"}
```

import java.util.concurrent.atomic.AtomicInteger;
import org.jspecify.annotations.NonNull;
import org.jspecify.annotations.Nullable;

/**
 * A comparator, with additional methods to support common operations. This is an "enriched" version
 * of {@code Comparator} for pre-Java-8 users, in the same sense that {@link FluentIterable} is an
 * enriched {@link Iterable} for pre-Java-8 users.
 *
 * <h3>Three types of methods</h3>
 *

   * the request has become less ready for future requests", i.e. its caches become stale, and
   * requests become more likely to trigger expensive operations (a more extreme case of this
   * example is when a server has just booted, and it is mostly busy with getting itself up to
   * speed).
   *

function for it to work correctly, otherwise the values will be different from what you expect (e.g. `QueryInfo` or something similar instead of `str`). And your editor won't complain, and Python won't complain running that function, only when the operations inside error out.

Because `Annotated` can have more than one metadata annotation, you could now even use the same function with other tools, like <a href="https://typer.tiangolo.com/" class="external-link" target="_blank">Typer</a>. 🚀...

In those cases, you can use the *path operation decorator* parameter `response_model` instead of the return type.

You can use the `response_model` parameter in any of the *path operations*:

* `@app.get()`
* `@app.post()`
* `@app.put()`
* `@app.delete()`
* etc.

{* ../../docs_src/response_model/tutorial001_py310.py hl[17,22,24:27] *}

/// note

Nesses casos, você pode usar o parâmetro `response_model` do *decorador de operação de rota* em vez do tipo de retorno.

Você pode usar o parâmetro `response_model` em qualquer uma das *operações de rota*:

* `@app.get()`
* `@app.post()`
* `@app.put()`
* `@app.delete()`
* etc.

{* ../../docs_src/response_model/tutorial001_py310.py hl[17,22,24:27] *}

/// note | Nota