@DisplayName("accept: name-based filter handles normal, empty, and null names")
    void accept_nameBasedFilter_handlesEdgeNames(String name, boolean expected) throws Exception {
        // Arrange: filter that accepts non-empty names ending with .txt
        SmbFileFilter filter = f -> {
            String n = f.getName();
            return n != null && !n.isEmpty() && n.endsWith(".txt");
        };
        when(smbFile.getName()).thenReturn(name);

  api(libs.square.kotlin.poet)
  testImplementation(libs.assertk)
  testImplementation(libs.junit.jupiter.api)
  testImplementation(libs.junit.jupiter.params)

  testImplementation(rootProject.libs.junit.jupiter.engine)
}

animalsniffer {
  isIgnoreFailures = true

### Crear un Engine { #create-an-engine }

Un `engine` de SQLModel (en el fondo, realmente es un `engine` de SQLAlchemy) es lo que **mantiene las conexiones** a la base de datos.

Tendrías **un solo objeto `engine`** para todo tu código para conectar a la misma base de datos.

jetbrains-annotations = { module = "org.jetbrains:annotations", version.ref = "jetbrains-annotations" }
junit-jupiter-api = { module = "org.junit.jupiter:junit-jupiter-api", version.ref = "org-junit-jupiter" }
junit-jupiter-engine = { module = "org.junit.jupiter:junit-jupiter-engine", version.ref = "org-junit-jupiter" }
junit-jupiter-params = { module = "org.junit.jupiter:junit-jupiter-params", version.ref = "org-junit-jupiter" }

    public void close() {
        scriptCache.invalidateAll();
        scriptCache.cleanUp();
    }

    /**
     * Returns the name identifier for this script engine.
     *
     * @return "groovy" - the identifier used to register and retrieve this engine
     */
    @Override
    protected String getName() {
        return "groovy";
    }

    /**

{* ../../docs_src/dependencies/tutorial013_an_py310.py ln[19:21] *}

...would be run after the response finishes sending the slow data:

{* ../../docs_src/dependencies/tutorial013_an_py310.py ln[30:38] hl[31:33] *}

But as `generate_stream()` doesn't use the database session, it is not really necessary to keep the session open while sending the response.

dependencies {
  "friendsApi"(projects.okhttp)
  api(projects.mockwebserver3)
  api(libs.junit.jupiter.api)
  compileOnly(libs.animalsniffer.annotations)

  testRuntimeOnly(libs.junit.jupiter.engine)
  testImplementation(libs.kotlin.junit5)
  testImplementation(projects.okhttpTestingSupport)
  testImplementation(libs.assertk)

OkCurl
======

_A curl for the next-generation web._

OkCurl is an OkHttp-backed curl clone which allows you to test OkHttp's HTTP engine (including
HTTP/2) against web servers.

To run locally, make sure you have GRAALVM_HOME set and run

```bash
./okcurl

# OpenAPI Webhooks { #openapi-webhooks }

There are cases where you want to tell your API **users** that your app could call *their* app (sending a request) with some data, normally to **notify** of some type of **event**.

This means that instead of the normal process of your users sending requests to your API, it's **your API** (or your app) that could **send requests to their system** (to their API, their app).

This is normally called a **webhook**.

    /** The expression used to match documents for boosting */
    private String matchExpression;

    /** The script engine type used for expression evaluation */
    private final String scriptType;

    /**
     * Default constructor that creates a DocBoostMatcher with default script type.
     * Uses the default script engine as defined in Constants.DEFAULT_SCRIPT.
     */
    public DocBoostMatcher() {