}
		data, err = io.ReadAll(plaintext)
		if err != nil {
			t.Fatalf("Test %d: failed to decrypt stream: %v", i, err)
		}

		if !bytes.Equal(data, test.Data) {
			t.Fatalf("Test %d: decrypted data does not match original data", i)
		}
	}
}

func BenchmarkEncrypt(b *testing.B) {
	key, err := hex.DecodeString("ddedadb867afa3f73bd33c25499a723ed7f9f51172ee7b1b679e08dc795debcc")
	if err != nil {

 */
@GwtCompatible
@NullUnmarked
final class UrlEscaperTesting {
  /**
   * Helper to assert common expected behaviour of uri escapers. You should call
   * assertBasicUrlEscaper() unless the escaper explicitly does not escape '%'.
   */
  @SuppressWarnings("nullness") // test of a bogus call
  static void assertBasicUrlEscaperExceptPercent(UnicodeEscaper e) {
    // URL escapers should throw null pointer exceptions for null input

 * <ul>
 *     <li>{@code jar}: Packages the project as a Java Archive (JAR) file.</li>
 *     <li>{@code war}: Packages the project as a Web Application Archive (WAR) file.</li>
 *     <li>{@code pom}: Indicates that the project does not produce a deployable artifact but is used for dependency management or as an aggregator.</li>
 *     <li>{@code maven-plugin}: Packages the project as a Maven plugin.</li>
 * </ul>
 *
 * <h2>Usage Example</h2>
 *

If your changes affect only the documentation, run:

    ./gradlew -p docs check

For more information about testing code examples in the documentation, see
https://github.com/elastic/elasticsearch/blob/master/docs/README.asciidoc

### Project layout

This repository is split into many top level directories. The most important
ones are:

#### `docs`
Documentation for the project.

#### `distribution`

            fail("Expected CurlException");
        } catch (Exception e) {
            assertTrue(e instanceof CurlException);
            assertTrue(e.getMessage().contains("The content does not exist"));
        }
    }

    @Test
    public void testGetContentAsStreamWithContentException() {
        CurlResponse response = new CurlResponse();

<searchConfiguration name="Method is annotated with @Provides but uses wrong naming" description="A service-providing method is annotated with `@Provides`, but its name does not start with 'create' or 'decorate', or is not 'configure'" suppressId="annotated_not_service_providing" problemDescriptor="Method is annotated with @Provides, but its name does not start with 'create' or 'decorate'" text="class $Class$ implements $Base$ {&#10;    @$Annotation$&#10;    @Modifier(&quot;Instance&quot;) $ReturnType$ $Method$...

    return asImmutableList(array);
  }

  /** Views the array as an immutable list. Checks for nulls; does not copy. */
  private static <E> ImmutableList<E> construct(Object... elements) {
    return asImmutableList(checkElementsNotNull(elements));
  }

  /**
   * Views the array as an immutable list. Does not check for nulls; does not copy.
   *
   * <p>The array must be internally created.
   */

   * `Synchronized` doesn't guarantee that it will hold the mutex for those calls because callers
   * are responsible for taking the mutex themselves:
   * https://docs.oracle.com/en/java/javase/22/docs/api/java.base/java/util/Collections.html#synchronizedCollection(java.util.Collection)
   *
   * Similarly, we avoid having those methods *implemented* in terms of *other* TestSet methods

   * collection is set to {@code null}. This is useful in determining the length of the collection
   * <i>only</i> if the caller knows that the collection does not contain any null elements.
   *
   * <p>This method returns the elements in the order they are returned by the collection's
   * iterator.
   *
   * <p>TODO(kevinb): support concurrently modified collections?

# デプロイ { #deployment }

**FastAPI** アプリケーションのデプロイは比較的簡単です。

## デプロイとは { #what-does-deployment-mean }

アプリケーションを**デプロイ**するとは、**ユーザーが利用できるようにする**ために必要な手順を実行することを意味します。

**Web API** の場合、通常は **リモートマシン** 上に配置し、優れたパフォーマンス、安定性などを提供する **サーバープログラム** と組み合わせて、**ユーザー** が中断や問題なく効率的にアプリケーションへ**アクセス**できるようにします。

これは **開発** 段階とは対照的です。開発では、コードを常に変更し、壊しては直し、開発サーバーを停止したり再起動したりします。

## デプロイ戦略 { #deployment-strategies }

具体的なユースケースや使用するツールによって、いくつかの方法があります。