@DisplayName("Test constructor with Configuration only")
    void testConstructorWithConfigOnly() {
        request = new Smb2QueryInfoRequest(mockConfig);

        assertNotNull(request);
        // SMB2_QUERY_INFO command value is 0x0010
        assertEquals((short) 0x0010, request.getCommand());

        // Verify that default file ID is set
        byte[] expectedFileId = Smb2Constants.UNSPECIFIED_FILEID;
        Field fileIdField;

### Migrer par étapes { #migrate-in-steps }

/// tip | Astuce

Essayez d'abord avec `bump-pydantic` ; si vos tests passent et que cela fonctionne, vous avez tout terminé en une seule commande. ✨

///

        void testAsServerMessageBlock2Response() {
            // Verify inheritance
            assertTrue(response instanceof ServerMessageBlock2);

            // Verify command can be retrieved from parent
            assertEquals(0, response.getCommand());
        }

        @Test
        @DisplayName("Should work with different buffer sizes")

* the background task: der Hintergrundtask
* the button: der Button
* the cloud provider: der Cloudanbieter
* the CLI: Das CLI
* the coverage: Die Testabdeckung
* the command line interface: Das Kommandozeileninterface
* the default value: der Defaultwert
* the default value: NOT der Standardwert
* the default declaration: die Default-Deklaration
* the deployment: das Deployment

"""
Top-level module of TensorFlow. By convention, we refer to this module as
`tf` instead of `tensorflow`, following the common practice of importing
TensorFlow via the command `import tensorflow as tf`.

The primary function of this module is to import all of the public TensorFlow
interfaces into a single place. The interfaces themselves are located in
sub-modules, as described below.

configuration itself can no longer be stored in the MinIO config file and
instead must be provided via environment variables. If you have set your KMS
configuration using e.g. the `mc admin config` commands you will need to adjust
your deployment.

Even though this change is backward compatible we do not expect that it affects
the vast majority of deployments in any negative way.

# Запустіть сервер вручну { #run-a-server-manually }

## Використовуйте команду `fastapi run` { #use-the-fastapi-run-command }

Коротко: використовуйте `fastapi run`, щоб запустити ваш застосунок FastAPI:

<div class="termy">

```console
$ <font color="#4E9A06">fastapi</font> run <u style="text-decoration-style:solid">main.py</u>

  <span style="background-color:#009485"><font color="#D3D7CF"> FastAPI </font></span>  Starting production server 🚀

            }

            sb.append(LS);
            sb.append(LS);
            sb.append(indentation);
            sb.append("Then, install it using the command: ");
            sb.append(LS);
            sb.append(indentation);
            sb.append("    mvn install:install-file -DgroupId=");
            sb.append(groupId);
            sb.append(" -DartifactId=");

# FastAPI CLI { #fastapi-cli }

**FastAPI <abbr title="command line interface - Kommandozeileninterface">CLI</abbr>** ist ein Kommandozeilenprogramm, mit dem Sie Ihre FastAPI-App bereitstellen, Ihr FastAPI-Projekt verwalten und mehr.

Wenn Sie FastAPI installieren (z. B. mit `pip install "fastapi[standard]"`), erhalten Sie ein Kommandozeilenprogramm, das Sie im Terminal ausführen können.

{* ../../docs_src/pydantic_v1_in_v2/tutorial004_an_py310.py hl[4,18] *}

### Migrate in steps { #migrate-in-steps }

/// tip

First try with `bump-pydantic`, if your tests pass and that works, then you're done in one command. ✨

///

If `bump-pydantic` doesn't work for your use case, you can use the support for both Pydantic v1 and v2 models in the same app to do the migration to Pydantic v2 gradually.