El beneficio de lanzar una excepción en lugar de `return`ar un valor será más evidente en la sección sobre Dependencias y Seguridad.

En este ejemplo, cuando el cliente solicita un ítem por un ID que no existe, lanza una excepción con un código de estado de `404`:

{* ../../docs_src/handling_errors/tutorial001.py hl[11] *}

O benefício de lançar uma exceção em vez de retornar um valor ficará mais evidente na seção sobre Dependências e Segurança.

Neste exemplo, quando o cliente pede, na requisição, por um item cujo ID não existe, a exceção com o status code `404` é lançada:

{* ../../docs_src/handling_errors/tutorial001.py hl[11] *}

### وابستگی‌ها

همین برای [وابستگی‌ها](tutorial/dependencies/index.md){.internal-link target=_blank} هم صدق می‌کنه. اگه یه وابستگی یه تابع `def` معمولی به جای `async def` باشه، توی استخر نخ خارجی اجرا می‌شه.

### زیروابستگی‌ها

---> 100%
```

</div>

A similar process would apply to any other ASGI server program.

/// tip

By adding the `standard`, Uvicorn will install and use some recommended extra dependencies.

That including `uvloop`, the high-performance drop-in replacement for `asyncio`, that provides the big concurrency performance boost.

        thumbnailManager.thumbnailTaskQueue = new LinkedBlockingQueue<>(100);
        thumbnailManager.generating = false;
    }

    // Test implementation of ThumbnailManager to avoid container dependencies
    private class TestThumbnailManager extends ThumbnailManager {
        @Override
        public void init() {
            // Do nothing to avoid container access
        }

        @Override

   *
   * @since 19.0
   */
  public static HashFunction concatenating(
      HashFunction first, HashFunction second, HashFunction... rest) {
    // We can't use Lists.asList() here because there's no hash->collect dependency
    List<HashFunction> list = new ArrayList<>();
    list.add(first);
    list.add(second);
    Collections.addAll(list, rest);
    return new ConcatenatedHashFunction(list.toArray(new HashFunction[0]));
  }

        // This is complex due to the class structure. A better approach would be
        // to refactor SmbFile to be more testable (e.g., dependency injection).
        // For now, we test methods that don't require deep mocks.
        return new SmbFile(url, auth);
    }

## Example Lambda handler

Install the necessary dependencies.
```sh
pip install flask requests
```

Following is an example lambda handler.
```py
from flask import Flask, request, abort, make_response
import requests

app = Flask(__name__)

    protected int maxDocumentCacheSize;

    /** Factory for creating ingesters to process documents */
    private IngestFactory ingestFactory = null;

    /**
     * Initializes the callback implementation after dependency injection.
     * Sets up configuration values and initializes the ingest factory if available.
     */
    @PostConstruct
    public void init() {
        if (logger.isDebugEnabled()) {

    protected List<Pair<String, Float>> additionalDefaultList = new ArrayList<>();

    /**
     * Initializes the query field configuration by loading field mappings from FessConfig.
     * This method is called after dependency injection is complete.
     * It sets up response fields, search fields, facet fields, sort fields, and other
     * field configurations based on the application configuration.
     */
    @PostConstruct