Because it's a Python exception, you don't `return` it, you `raise` it.

This also means that if you are inside a utility function that you are calling inside of your *path operation function*, and you raise the `HTTPException` from inside of that utility function, it won't run the rest of the code in the *path operation function*, it will terminate that request right away and send the HTTP error from the `HTTPException` to the client.

not first set to `PENDING` state.

This is a slower operation that does not use replication queues and is designed to walk the namespace and replicate objects one at a time so as not to impede server load. Ideally, resync should not be initiated for multiple buckets simultaneously - progress of the syncing can be monitored by looking at `mc replicate resync status alias/bucket --remote-bucket <arn>`. In the event that resync operation failed to replicate some versions, they would be picked up...

If you pass a "callable" as a dependency in **FastAPI**, it will analyze the parameters for that "callable", and process them in the same way as the parameters for a *path operation function*. Including sub-dependencies.

That also applies to callables with no parameters at all. The same as it would be for *path operation functions* with no parameters.

Then, we can change the dependency "dependable" `common_parameters` from above to the class `CommonQueryParams`:

## Additional Response with `model` { #additional-response-with-model }

You can pass to your *path operation decorators* a parameter `responses`.

It receives a `dict`: the keys are status codes for each response (like `200`), and the values are other `dict`s with the information for each of them.

            result = buf.dec_ndr_long();
        } else { /* Bind_ack or Response */
            decode_out(buf);
        }
    }

    /**
     * Get the operation number for this DCERPC message.
     * @return the operation number
     */
    public abstract int getOpnum();

    /**
     * Encode the input parameters for this DCERPC message.
     * @param buf the buffer to encode into

Similarly, you cannot redefine a path operation:

{* ../../docs_src/path_params/tutorial003b.py hl[6,11] *}

The first one will always be used since the path matches first.

## Predefined values { #predefined-values }

De manera similar, no puedes redefinir una path operation:

{* ../../docs_src/path_params/tutorial003b.py hl[6,11] *}

La primera siempre será utilizada ya que el path coincide primero.

## Valores predefinidos

///

Este parámetro no crea ese endpoint / *path operation*, pero declara que la URL `/token` será la que el cliente deberá usar para obtener el token. Esa información se usa en OpenAPI, y luego en los sistemas de documentación interactiva del API.

Pronto también crearemos la verdadera *path operation*.

/// info | Información

     * Maybe semantics packet flag
     */
    int RPC_C_PF_MAYBE = 0x04;
    /**
     * Idempotent operation packet flag
     */
    int RPC_C_PF_IDEMPOTENT = 0x08;
    /**
     * Broadcast with maybe semantics packet flag
     */
    int RPC_C_PF_BROADCAST_MAYBE = 0x10;
    /**
     * Not idempotent operation packet flag
     */
    int RPC_C_PF_NOT_IDEMPOTENT = 0x20;
    /**

* A particular program while it is **running** on the operating system.
    * This doesn't refer to the file, nor to the code, it refers **specifically** to the thing that is being **executed** and managed by the operating system.
* Any program, any code, **can only do things** when it is being **executed**. So, when there's a **process running**.