///

## A database dependency with `yield` { #a-database-dependency-with-yield }

For example, you could use this to create a database session and close it after finishing.

Only the code prior to and including the `yield` statement is executed before creating a response:

{* ../../docs_src/dependencies/tutorial007.py hl[2:4] *}

The yielded value is what is injected into *path operations* and other dependencies:

Using resources from dependencies with `yield` in background tasks is no longer supported.

This change is what supports the new features, read below. 🤓

### Dependencies with `yield`, `HTTPException` and Background Tasks

Dependencies with `yield` now can raise `HTTPException` and other exceptions after `yield`. 🎉

{* ../../docs_src/events/tutorial003.py hl[14:19] *}

The first part of the function, before the `yield`, will be executed **before** the application starts.

And the part after the `yield` will be executed **after** the application has finished.

### Async Context Manager { #async-context-manager }

        assertEquals(expectedNt, actual.get(), String.format("NTSTATUS for %08x should be %08x", dosErr, expectedNt));
    }

    @Test
    @DisplayName("Unknown DOS error code yields empty Optional")
    void testUnknownCode() {
        Optional<Integer> noMatch = findNtStatus(0xdeadbeef);
        assertFalse(noMatch.isPresent(), "Mapping for unknown code should be absent");
    }

    @Test

                        tree.acquire();
                        successCount.incrementAndGet();

                        // Small delay to increase chance of race conditions
                        Thread.yield();
                    }
                } catch (Exception e) {
                    exceptions.add(e);
                } finally {
                    endLatch.countDown();
                }
            });

        case TIME_1601_NANOS_64BE -> {
            t = (date.getTime() + MILLISECONDS_BETWEEN_1970_AND_1601) * 10000L;
            yield enc_uint64be(t, dst, di);
        }
        case TIME_1601_NANOS_64LE -> {
            t = (date.getTime() + MILLISECONDS_BETWEEN_1970_AND_1601) * 10000L;
            yield enc_uint64le(t, dst, di);
        }
        case TIME_1970_MILLIS_64BE -> enc_uint64be(date.getTime(), dst, di);

            t = (date.getTime() + SmbConstants.MILLISECONDS_BETWEEN_1970_AND_1601) * 10000L;
            yield enc_uint64be(t, dst, di);
        }
        case TIME_1601_NANOS_64LE -> {
            t = (date.getTime() + SmbConstants.MILLISECONDS_BETWEEN_1970_AND_1601) * 10000L;
            yield enc_uint64le(t, dst, di);
        }
        case TIME_1970_MILLIS_64BE -> enc_uint64be(date.getTime(), dst, di);

1. This is the generator function. It's a "generator function" because it contains `yield` statements inside.
2. By using a `with` block, we make sure that the file-like object is closed after the generator function is done. So, after it finishes sending the response.
3. This `yield from` tells the function to iterate over that thing named `file_like`. And then, for each part iterated, yield that part as coming from this generator function (`iterfile`).

    @DisplayName("available() on SMB1 returns 0 and marks closed on disconnected statuses")
    void available_smb1_disconnectedStatuses(int status) throws Exception {
        // Verify SMB1 path: disconnected/server-closed statuses yield 0 and mark fd closed
        SmbPipeInputStream stream = newStreamWithInit(false);

        when(handle.ensureOpen()).thenReturn(fd);
        when(fd.getTree()).thenReturn(tree);

class StaticJAASConfigurationTest {

    // Constants used in assertions
    private static final String EXPECTED_LOGIN_MODULE = "com.sun.security.auth.module.Krb5LoginModule";

    @Test
    @DisplayName("Default constructor yields REQUIRED Krb5 entry with empty options")
    void defaultConstructor_producesRequiredKrb5EntryWithEmptyOptions() {
        // Arrange
        StaticJAASConfiguration cfg = new StaticJAASConfiguration();

        // Act