testImplementation(libs.kotlin.junit5)
  testImplementation(libs.junit.jupiter.params)
}

graalvmNative {
  testSupport = true

  binaries {
    named("test") {
      buildArgs.add("--strict-image-heap")

      // speed up development testing
      buildArgs.add("-Ob")
    }
  }

.brand-image-xl.single {\n  margin-top: -.3rem;\n}\n\n.brand-link.text-sm .brand-image,\n.text-sm .brand-link .brand-image {\n  height: 29px;\n  margin-bottom: -.25rem;\n  margin-left: .95rem;\n  margin-top: -.25rem;\n}\n\n.brand-link.text-sm .brand-image-xs,\n.text-sm .brand-link .brand-image-xs {\n  margin-top: -.2rem;\n  max-height: 29px;\n}\n\n.brand-link.text-sm .brand-image-xl,\n.text-sm .brand-link .brand-image-xl {\n  margin-top: -.225rem;\n  max-height: 38px;\n}\n\n.main-sidebar {\n  height: 100vh;\n...

* kubectl rolling-update support for same image ([#24645](https://github.com/kubernetes/kubernetes/pull/24645), [@jlowdermilk](https://github.com/jlowdermilk))
* Add an entry to the salt config to allow Debian jessie on GCE. ([#25123](https://github.com/kubernetes/kubernetes/pull/25123), [@jlewi](https://github.com/jlewi))
    * As with the existing Wheezy image on GCE, docker is expected to already be installed in the image.

* Update amd64 kube-proxy base image to debian-iptables-amd64:v5 ([#39725](https://github.com/kubernetes/kubernetes/pull/39725), [@ixdy](https://github.com/ixdy))
* Update kube-proxy image to be based off of Debian 8.6 base image. ([#39695](https://github.com/kubernetes/kubernetes/pull/39695), [@ixdy](https://github.com/ixdy))

///

### Nicht-async-*Pfadoperation-Funktionen* { #non-async-path-operation-functions }

Sie können auch normale `def`-Funktionen (ohne `async`) verwenden und `yield` genauso einsetzen.

FastAPI stellt sicher, dass sie korrekt ausgeführt wird, sodass sie die Event Loop nicht blockiert.

 * Example usage:
 * <pre>
 * public class CustomPackagingProvider implements PackagingProvider {
 *     public Collection&lt;Packaging&gt; provides() {
 *         return Arrays.asList(
 *             packaging("docker-image"),
 *             packaging("flatpak")
 *         );
 *     }
 * }
 * </pre>
 *
 * @see org.apache.maven.api.Packaging
 * @see org.apache.maven.api.spi.ExtensibleEnumProvider
 * @since 4.0.0
 */

	  ## NOTE: metadata filter not supported when "source" is non MinIO.
	  # metadata:
	  #   - key: "content-type"
	  #     value: "image/*" # match objects with 'content-type', with all values starting with 'image/'

	notify:
	  endpoint: "https://notify.endpoint" # notification endpoint to receive job status events
	  token: "Bearer xxxxx" # optional authentication token for the notification endpoint

 * public class CustomTypeProvider implements TypeProvider {
 *     public Collection<Type> provides() {
 *         return Arrays.asList(
 *             type("kotlin-library", "jar", "kotlin"),
 *             type("docker-image", "tar.gz", null)
 *         );
 *     }
 * }
 * </pre>
 *
 * @see org.apache.maven.api.Type
 * @see org.apache.maven.api.spi.ExtensibleEnumProvider
 * @since 4.0.0
 */
@Experimental
@Consumer

  }

  public void testWithoutParameters() {
    assertThat(MediaType.parse("image/gif").withoutParameters())
        .isSameInstanceAs(MediaType.parse("image/gif"));
    assertEquals(
        MediaType.parse("image/gif"), MediaType.parse("image/gif; foo=bar").withoutParameters());
  }

  public void testWithParameters() {
    assertEquals(

/// info | 情報

`Offer`は`Item`のリストであり、それらがさらにオプションの`Image`のリストを持っていることに注目してください。

///

## 純粋なリストのボディ { #bodies-of-pure-lists }

期待するJSONボディのトップレベルの値がJSON`array`（Pythonの`list`）であれば、Pydanticモデルと同じように、関数のパラメータで型を宣言することができます:

```Python
images: list[Image]
```

以下のように:

{* ../../docs_src/body_nested_models/tutorial008_py310.py hl[13] *}