```

</div>

La réponse sera semblable à :

```JSON
{
    "message": "Hello World",
    "root_path": "/api/v1"
}
```

### Définir le `root_path` dans l'application FastAPI { #setting-the-root-path-in-the-fastapi-app }

```

</div>

A resposta seria algo como:

```JSON
{
    "message": "Hello World",
    "root_path": "/api/v1"
}
```

### Configurando o `root_path` na aplicação FastAPI { #setting-the-root-path-in-the-fastapi-app }

Alternativamente, se você não tiver uma maneira de fornecer uma opção de linha de comando como `--root-path` ou equivalente, você pode definir o parâmetro `root_path` ao criar sua aplicação FastAPI:

    private long getSerialVersionUID() {
        try {
            java.lang.reflect.Field field = FessMessages.class.getDeclaredField("serialVersionUID");
            field.setAccessible(true);
            return field.getLong(null);
        } catch (Exception e) {
            fail("Failed to get serialVersionUID: " + e.getMessage());
            return -1;
        }
    }

    // Test error message methods without parameters

            assertDoesNotThrow(() -> request.setFileId(standardFileId));
            assertDoesNotThrow(() -> request.setFileId(longFileId));
        }
    }

    @Nested
    @DisplayName("Parameter Setting Tests")
    class ParameterSettingTests {

        @Test
        @DisplayName("Should set padding correctly")
        void testSetPadding() {
            assertDoesNotThrow(() -> request.setPadding((byte) 0));

## Vous êtes pressés ? { #in-a-hurry }

<abbr title="too long; didn't read - trop long ; pas lu"><strong>TL;DR :</strong></abbr>

Si vous utilisez des bibliothèques tierces qui nécessitent d'être appelées avec `await`, telles que :

```Python
results = await some_library()
```

        // First call to initialize
        testFactory.getDataStoreNames();

        final long[] observedTimes = new long[10];
        final Thread[] threads = new Thread[10];

        // Trigger cache refresh by setting old time
        testFactory.lastLoadedTime = System.currentTimeMillis() - 70000L;

        // One thread updates
        Thread updater = new Thread(() -> {
            testFactory.getDataStoreNames();
        });

 * and {@link java.net.InetAddress}. The name resolution mechanisms
 * used will systematically query all available configured resolution
 * services including WINS, broadcasts, DNS, and LMHOSTS. See
 * <a href="../../resolver.html">Setting Name Resolution Properties</a>
 * and the <code>jcifs.smb1.resolveOrder</code> property. Changing
 * jCIFS name resolution properties can greatly affect the behavior of
 * the client and may be necessary for proper operation.

                warnings.simplefilter(
                    "ignore", category=UnsupportedFieldAttributeWarning
                )
            # TODO: remove after setting the min Pydantic to v2.12.3
            # that adds asdict(), and use self.field_info.asdict() instead
            field_dict = asdict(self.field_info)
            annotated_args = (
                field_dict["annotation"],

const preparedStmtDBKey = "preparedStmt"

// Config GORM config
type Config struct {
	// GORM perform single create, update, delete operations in transactions by default to ensure database data integrity
	// You can disable it by setting `SkipDefaultTransaction` to true
	SkipDefaultTransaction    bool
	DefaultTransactionTimeout time.Duration
	DefaultContextTimeout     time.Duration

	// NamingStrategy tables, columns naming strategy

	tx = db.getInstance()
	tx.Statement.assigns = attrs
	return
}

// Unscoped disables the global scope of soft deletion in a query.
// By default, GORM uses soft deletion, marking records as "deleted"
// by setting a timestamp on a specific field (e.g., `deleted_at`).
// Unscoped allows queries to include records marked as deleted,
// overriding the soft deletion behavior.
// Example:
//
//	var users []User