Es war beispielsweise klar, dass es idealerweise auf Standard-Python-Typhinweisen basieren sollte.

Der beste Ansatz bestand außerdem darin, bereits bestehende Standards zu nutzen.

        executor.shutdown();

        // Circuit breaker should have handled concurrent operations
        assertTrue(successCount.get() > 0, "Should have some successful operations");
        assertTrue(failureCount.get() > 0, "Should have some failed operations");
    }

    @Test
    public void testHalfOpenMaxAttempts() throws Exception {
        // Open circuit

	if sepIndex == -1 {
		return nil, fmt.Errorf("'%s' does not have a valid range value", rangeString)
	}

	offsetBeginString := byteRangeString[:sepIndex]
	offsetBegin := int64(-1)
	// Convert offsetBeginString only if its not empty.
	if len(offsetBeginString) > 0 {
		if offsetBeginString[0] == '+' {
			return nil, fmt.Errorf("Byte position ('%s') must not have a sign", offsetBeginString)

In fact, in some cases, it will even have **two JSON Schemas** in OpenAPI for the same Pydantic model, for input and output, depending on if they have **default values**.

Let's see how that works and how to change it if you need to do that.

## Pydantic Models for Input and Output { #pydantic-models-for-input-and-output }

Let's say you have a Pydantic model with default values, like this one:

* **Uvicorn**:
    * Will have the best performance, as it doesn't have much extra code apart from the server itself.

            assertNotNull(clazz.getMethod("getName"), "Should have getName method");
            assertNotNull(clazz.getMethod("getType"), "Should have getType method");
            assertNotNull(clazz.getMethod("exists"), "Should have exists method");
            assertNotNull(clazz.getMethod("resolve", String.class), "Should have resolve method");
            assertNotNull(clazz.getMethod("close"), "Should have close method");

```console
// Você pode criar uma variável de ambiente MY_NAME com
$ export MY_NAME="Wade Wilson"

// Então você pode usá-la com outros programas, como
$ echo "Hello $MY_NAME"

Hello Wade Wilson
```

</div>

////

//// tab | Windows PowerShell

<div class="termy">

```console
// Criar uma variável de ambiente MY_NAME
$ $Env:MY_NAME = "Wade Wilson"

// Usá-la com outros programas, como

/// tip

Notice the autocompletion for `name` and `price`, that was defined in the FastAPI application, in the `Item` model.

///

You will have inline errors for the data that you send:

<img src="/img/tutorial/generate-clients/image04.png">

The response object will also have autocompletion:

<img src="/img/tutorial/generate-clients/image05.png">

## FastAPI App with Tags { #fastapi-app-with-tags }

    }

    @Test
    @DisplayName("Should have correct dialect codes for SMB2+ versions")
    void testDialectCodes() {
        // SMB1 should throw UnsupportedOperationException
        assertThrows(UnsupportedOperationException.class, () -> {
            DialectVersion.SMB1.getDialect();
        });

        // SMB2+ versions should have valid dialect codes
        assertTrue(DialectVersion.SMB202.getDialect() > 0);

But `OAuth2PasswordRequestForm` is just a class dependency that you could have written yourself, or you could have declared `Form` parameters directly.

But as it's a common use case, it is provided by **FastAPI** directly, just to make it easier.

///

### Use the form data { #use-the-form-data }

/// tip