}
        toEvict.socket().closeQuietly()
        connectionListener.connectionClosed(toEvict)
        if (connections.isEmpty()) cleanupQueue.cancelAll()

        // Clean up again immediately.
        return 0L
      }

      earliestEvictableConnection != null -> {
        // A connection will be ready to evict soon.
        return earliestEvictableIdleAtNs + keepAliveDurationNs - now

        // Add multiple resource source roots
        project.addSourceRoot(
                new DefaultSourceRoot(ProjectScope.MAIN, Language.RESOURCES, Path.of("src/main/resources2")));
        project.addSourceRoot(
                new DefaultSourceRoot(ProjectScope.MAIN, Language.RESOURCES, Path.of("src/main/resources3")));

        // Verify initial order
        List<Resource> resources = project.getResources();

    @DisplayName("releaseBuffer and getBuffer should implement buffer reuse")
    void testBufferReuse() {
        // Given
        byte[] originalBuffer = testCache.getBuffer();

        // When - release and get again
        testCache.releaseBuffer(originalBuffer);
        byte[] reusedBuffer = testCache.getBuffer();

        // Then
        assertSame(originalBuffer, reusedBuffer, "Released buffer should be reused");
    }

 *
 * <p>The {@code Iterable} specification does not make it absolutely clear what should happen on a
 * second invocation, so implementors have made various choices, including:
 *
 * <ul>
 *   <li>returning the same iterator again
 *   <li>throwing an exception of some kind
 *   <li>or the usual, <i>robust</i> behavior, which all known {@link Collection} implementations
 *       have, of returning a new, independent iterator
 * </ul>
 *

<div class="termy">

```console
// Aquí todavía no configuramos la env var
$ python main.py

// Como no configuramos la env var, obtenemos el valor por defecto

Hello World from Python

// Pero si creamos una variable de entorno primero
$ export MY_NAME="Wade Wilson"

// Y luego llamamos al programa nuevamente
$ python main.py

// Ahora puede leer la variable de entorno

Hello Wade Wilson from Python
```

    val newTags = tags.plus(type, computed)
    if (compareAndSet(tags, newTags)) return computed

    // We lost the race. Possibly to other code that was putting a *different* key. Try again!
  }

                // Retrying only makes sense if the invalid parameter is an tree id. If we have a stale file descriptor
                // retrying make no sense, as it will never become available again.
                if (params.contains(RequestParam.NO_RETRY)
                        || !(smbe.getCause() instanceof TransportException) && smbe.getNtStatus() != NtStatus.NT_STATUS_INVALID_PARAMETER) {

```
.
├── app
│   ├── __init__.py
│   ├── main.py
│   └── test_main.py
```

The file `main.py` would have:

{* ../../docs_src/async_tests/app_a_py39/main.py *}

The file `test_main.py` would have the tests for `main.py`, it could look like this now:

{* ../../docs_src/async_tests/app_a_py39/test_main.py *}

## Run it { #run-it }

///

## Модуль main в `FastAPI` { #the-main-fastapi }

Теперь давайте посмотрим на модуль `app/main.py`.

Именно сюда вы импортируете и именно здесь вы используете класс `FastAPI`.

Это основной файл вашего приложения, который объединяет всё в одно целое.

И теперь, когда большая часть логики приложения разделена на отдельные модули, основной файл `app/main.py` будет достаточно простым.

    val requestSendStarted = e !is ConnectionShutdownException

    // The application layer has forbidden retries.
    if (!client.retryOnConnectionFailure) return false

    // We can't send the request body again.
    if (requestSendStarted && requestIsOneShot(e, userRequest)) return false

    // This exception is fatal.
    if (!isRecoverable(e, requestSendStarted)) return false

    // No more routes to attempt.