final int index = i;
            threads[i] = new Thread(() -> {
                for (int j = 0; j < 100; j++) {
                    String name = "file" + index + "_" + j + ".txt";
                    entry.updateChild(name, j * 100L, j * 1000L, false, 0x20, j * 500L, j * 800L);
                }
            });
            threads[i].start();
        }

{* ../../docs_src/templates/tutorial001_py310.py hl[4,11,15:18] *}

/// note | 備考

FastAPI 0.108.0、Starlette 0.29.0 以前では、`name` は最初のパラメータでした。

またそれ以前のバージョンでは、`request` オブジェクトは Jinja2 用のコンテキスト内のキーと値のペアの一部として渡されていました。

///

/// tip | 豆知識

`response_class=HTMLResponse` を宣言すると、ドキュメント UI がレスポンスが HTML であることを認識できます。

///

}

type azureConf struct {
	madmin.TierAzure
}

func (conf azureConf) Validate() error {
	switch {
	case conf.AccountName == "":
		return errors.New("the account name is required")
	case conf.AccountKey != "" && (conf.SPAuth.TenantID != "" || conf.SPAuth.ClientID != "" || conf.SPAuth.ClientSecret != ""):
		return errors.New("multiple authentication mechanisms are provided")

        } catch (final IOException e) {
            throw new DictionaryException("Failed to parse " + path, e);
        }
    }

    /**
     * Returns the simple file name (without directory path) of this mapping file.
     *
     * @return the file name without the full path
     */
    public String getSimpleName() {
        return new File(path).getName();
    }

    /**

		<button type="button" class="btn-close" data-bs-dismiss="offcanvas" aria-label="Close"></button>
	</div>
	<div class="offcanvas-body">
		<c:forEach var="fieldData" items="${facetResponse.fieldList}">
			<c:if test="${fieldData.name == 'label' && fieldData.valueCountMap.size() > 0}">
				<ul class="list-group mb-2">
					<li class="list-group-item text-uppercase"><la:message key="labels.facet_label_title" /></li>

            }

            @Override
            public String[] getExtraQueries() {
                return extraQueries;
            }

            @Override
            public Object getAttribute(String name) {
                return null;
            }

            @Override
            public Locale getLocale() {
                return null;
            }

            @Override

        if (message == null || message.isEmpty()) {
            return String.format("[%s] %s", errorCode.name(), errorCode.getDescription());
        }
        return String.format("[%s] %s: %s", errorCode.name(), errorCode.getDescription(), message);
    }

    private String extractOperationName() {
        StackTraceElement[] stack = Thread.currentThread().getStackTrace();

        }
    }

    @Test
    @DisplayName("Test toString contains proper class name")
    void testToStringFormat() {
        String str = response.toString();

        // Should start with the class name
        assertTrue(str.startsWith("Trans2SetFileInformationResponse["));

        // Should end with closing bracket
        assertTrue(str.endsWith("]"));

OAuth2 spezifiziert, dass der Client/Benutzer bei Verwendung des „Password Flow“ (den wir verwenden) die Felder `username` und `password` als Formulardaten senden muss.

Und die Spezifikation sagt, dass die Felder so benannt werden müssen. `user-name` oder `email` würde also nicht funktionieren.

Aber keine Sorge, Sie können sie Ihren Endbenutzern im Frontend so anzeigen, wie Sie möchten.

Und Ihre Datenbankmodelle können beliebige andere Namen verwenden.

OAuth2 specifies that when using the "password flow" (that we are using) the client/user must send a `username` and `password` fields as form data.

And the spec says that the fields have to be named like that. So `user-name` or `email` wouldn't work.

But don't worry, you can show it as you wish to your final users in the frontend.

And your database models can use any other names you want.