try {
            // Create a new instance to ensure clean state
            SystemMonitorTarget testTarget = new SystemMonitorTarget();

            // Try to call the expired method
            // Note: This method may fail in test environments due to system dependencies
            // but we mainly want to ensure the method signature is correct
            testTarget.expired();

In this case, you will have to ensure that each operation ID is **unique** in some other way.

For example, you could make sure that each *path operation* has a tag, and then generate the operation ID based on the **tag** and the *path operation* **name** (the function name).

### Custom Generate Unique ID Function { #custom-generate-unique-id-function }

# General - How To - Recipes { #general-how-to-recipes }

Here are several pointers to other places in the docs, for general or frequent questions.

## Filter Data - Security { #filter-data-security }

To ensure that you don't return more data than you should, read the docs for [Tutorial - Response Model - Return Type](../tutorial/response-model.md){.internal-link target=_blank}.

## Documentation Tags - OpenAPI { #documentation-tags-openapi }

    }

    @Test
    @DisplayName("Should create new connections when reuse conditions are not met")
    void testNoConnectionReuse() throws Exception {
        // Given: Create a new pool for this test to ensure isolation
        SmbTransportPoolImpl testPool = new SmbTransportPoolImpl();
        when(ctx.getTransportPool()).thenReturn(testPool);

        // Create an existing connection

/// tip

Note that we're using async/await with the new `AsyncClient` - the request is asynchronous.

///

/// warning

If your application relies on lifespan events, the `AsyncClient` won't trigger these events. To ensure they are triggered, use `LifespanManager` from <a href="https://github.com/florimondmanca/asgi-lifespan#usage" class="external-link" target="_blank">florimondmanca/asgi-lifespan</a>.

///

            SmbTransportImpl transport = new SmbTransportImpl(context, serverUniAddress, port, localAddress, localPort, forceSigning);

            // Ensure the transport is connected and ready
            transport.ensureConnected();

            // Verify multi-channel capability (SMB3+ required)

To handle that, we first convert the `username` and `password` to `bytes` encoding them with UTF-8.

Then we can use `secrets.compare_digest()` to ensure that `credentials.username` is `"stanleyjobson"`, and that `credentials.password` is `"swordfish"`.

{* ../../docs_src/security/tutorial007_an_py39.py hl[1,12:24] *}

This would be similar to:

```Python

            auth3.close();
            auth4.close();
        } finally {
            auth1.close();
            auth2.close();
        }
    }

    /**
     * Test concurrent password comparisons to ensure thread safety and consistent timing.
     */
    @Test
    public void testConcurrentTimingConsistency() throws Exception {
        final char[] password = "concurrenttestpassword".toCharArray();

It also re-declares `id: int`. By doing this, we are making a **contract** with the API clients, so that they can always expect the `id` to be there and to be an `int` (it will never be `None`).

/// tip

Having the return model ensure that a value is always available and always `int` (not `None`) is very useful for the API clients, they can write much simpler code having this certainty.

<img src="/img/tutorial/body/image04.png">

This is not by chance, the whole framework was built around that design.

And it was thoroughly tested at the design phase, before any implementation, to ensure it would work with all the editors.

There were even some changes to Pydantic itself to support this.