nindent 4 }} {{- end }} spec: jobName: {{ template "minio.fullname" . }} {{- if .Values.tls.enabled }} tlsConfig: ca: secret: name: {{ .Values.tls.certSecret }} key: {{ .Values.tls.publicCrt }} serverName: {{ template "minio.fullname" . }} {{- end }} prober: url: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}:{{ .Values.service.port }} path: /minio/v2/metrics/cluster {{- if .Values.tls.enabled }} scheme: https {{- else }} scheme: http {{- end }} {{- if .Values.metrics.serviceMonitor.relabelConfigsCluste...

    List<?> exp = copyToList(expected);
    List<?> act = copyToList(actual);
    String actString = act.toString();

    // Of course we could take pains to give the complete description of the
    // problem on any failure.

    // Yeah it's n^2.
    for (Object object : exp) {
      if (!act.remove(object)) {
        fail(
            "did not contain expected element "
                + object

  static <V extends @Nullable Object> V getDoneValue(Object obj) throws ExecutionException {
    // While this seems like it might be too branch-y, simple benchmarking proves it to be
    // unmeasurable (comparing done AbstractFutures with immediateFuture)
    if (obj instanceof Cancellation) {
      Cancellation cancellation = (Cancellation) obj;
      Throwable cause = cancellation.cause;

   * not a seed, and because that size is rounded up. Thus, {@code goodFastHash} instances with
   * different parameters can be equal. That fact is a problem for {@code
   * testSeededHashFunctionEquals}.
   */
  public void testGoodFastHashEquals() throws Exception {
    HashFunction hashFunction1a = Hashing.goodFastHash(1);

#### Dict { #dict }

定義 `dict` 時，你需要傳入 2 個以逗號分隔的型別參數。

第一個型別參數是 `dict` 的鍵（key）。

第二個型別參數是 `dict` 的值（value）：

{* ../../docs_src/python_types/tutorial008_py310.py hl[1] *}

這代表：

* 變數 `prices` 是個 `dict`：
    * 這個 `dict` 的鍵是 `str`（例如每個項目的名稱）。
    * 這個 `dict` 的值是 `float`（例如每個項目的價格）。

#### Union { #union }

你可以宣告一個變數可以是「多種型別」中的任一種，例如 `int` 或 `str`。

Und es generiert OpenAPI-Schemas.

So funktioniert es in Flask, Starlette, Responder, usw.

Aber dann haben wir wieder das Problem einer Mikrosyntax innerhalb eines Python-Strings (eines großen YAML).

labels.oic_base_url=Base URL
labels.oic_default_groups=Default Groups
labels.oic_default_roles=Default Roles
labels.general_menu_saml=SAML
labels.saml_sp_base_url=SP Base URL
labels.saml_attribute_group_name=Group Attribute Name
labels.saml_attribute_role_name=Role Attribute Name
labels.saml_default_groups=Default Groups
labels.saml_default_roles=Default Roles
labels.general_menu_spnego=SPNEGO
labels.spnego_krb5_conf=Krb5 Config

last the Dodo said, `EVERYBODY has won, and all must have
prizes.'

  `But who is to give the prizes?' quite a chorus of voices
asked.

  `Why, SHE, of course,' said the Dodo, pointing to Alice with
one finger; and the whole party at once crowded round her,
calling out in a confused way, `Prizes! Prizes!'

  Alice had no idea what to do, and in despair she put her hand

* the task function

* the template
* the template engine

* the type annotation
* the type hint

* the server worker
* the Uvicorn worker
* the Gunicorn Worker
* the worker process
* the worker class
* the workload

* the deployment
* to deploy

* the SDK
* the software development kit

* the `APIRouter`
* the `requirements.txt`
* the Bearer Token

{* ../../docs_src/response_model/tutorial002_py310.py hl[16] *}

Now, whenever a browser is creating a user with a password, the API will return the same password in the response.

In this case, it might not be a problem, because it's the same user sending the password.

But if we use the same model for another *path operation*, we could be sending our user's passwords to every client.

/// danger