* set a value to {@code null} will result in a {@link NullPointerException}.
   *
   * <p>The returned list maintains the values, but not the identities, of {@code Double} objects
   * written to or read from it. For example, whether {@code list.get(0) == list.get(0)} is true for
   * the returned list is unspecified.
   *
   * <p>The returned list may have unexpected behavior if it contains {@code NaN}, or if {@code NaN}

If the capacity is zero or absent, the channel is unbuffered and communication
succeeds only when both a sender and receiver are ready. Otherwise, the channel
is buffered and communication succeeds without blocking if the buffer
is not full (sends) or not empty (receives).
A <code>nil</code> channel is never ready for communication.
</p>

<p>
A channel may be closed with the built-in function

        helper.tryStartOperation("test_op");
        assertNull(passedData.get());
    }

    @Test
    public void test_tryStartOperation_twoArg_usesConfigRetry() {
        // tryStartOperation(name, data) should read maxRetry from FessConfig
        final AtomicInteger passedRetries = new AtomicInteger(-1);
        final CoordinatorHelper helper = new CoordinatorHelper() {
            @Override

Détails sur la syntaxe `async def` pour les *fonctions de chemin d'accès* et quelques rappels sur le code asynchrone, la concurrence et le parallélisme.

## 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()
```

        for (int t = 0; t < threadCount; t++) {
            final int threadId = t;
            executor.submit(() -> {
                try {
                    startLatch.await(); // Wait for all threads to be ready

                    for (int i = 0; i < operationsPerThread; i++) {
                        String message = String.format("Thread-%d-Message-%d", threadId, i);
                        byte[] plaintext = message.getBytes();

    - [Container Images](#container-images-3)
  - [Changelog since v1.34.0](#changelog-since-v1340)
  - [Urgent Upgrade Notes](#urgent-upgrade-notes)
    - [(No, really, you MUST read this before you upgrade)](#no-really-you-must-read-this-before-you-upgrade)
  - [Changes by Kind](#changes-by-kind-3)
    - [Deprecation](#deprecation)
    - [API Change](#api-change)
    - [Feature](#feature-2)
    - [Documentation](#documentation)

pkg io, type ReadCloser interface { Close, Read }
pkg io, type ReadCloser interface, Close() error
pkg io, type ReadCloser interface, Read([]uint8) (int, error)
pkg io, type ReadSeeker interface { Read, Seek }
pkg io, type ReadSeeker interface, Read([]uint8) (int, error)
pkg io, type ReadSeeker interface, Seek(int64, int) (int64, error)
pkg io, type ReadWriteCloser interface { Close, Read, Write }

 * in the {@link Iterators} class.
 *
 * <p><b>Java 8+ users:</b> several common uses for this class are now more comprehensively
 * addressed by the new {@link java.util.stream.Stream} library. Read the method documentation below
 * for comparisons. This class is not being deprecated, but we gently encourage you to migrate to
 * streams.
 *

프로젝트 작업을 마쳤다면 가상 환경을 **비활성화**할 수 있습니다.

<div class="termy">

```console
$ deactivate
```

</div>

이렇게 하면 `python`을 실행할 때, 해당 가상 환경과 그 안에 설치된 패키지에서 실행하려고 하지 않습니다.

## 작업할 준비 완료 { #ready-to-work }

이제 프로젝트 작업을 시작할 준비가 되었습니다.



/// tip

위의 내용이 무엇인지 더 이해하고 싶으신가요?

계속 읽어보세요. 👇🤓

///

## 가상 환경을 왜 사용하나요 { #why-virtual-environments }

# 並行與 async / await { #concurrency-and-async-await }

有關*路徑操作函式*的 `async def` 語法的細節與非同步 (asynchronous) 程式碼、並行 (concurrency) 與平行 (parallelism) 的一些背景知識。

## 趕時間嗎? { #in-a-hurry }

<abbr title="too long; didn't read - 太長不看"><strong>TL;DR:</strong></abbr>

如果你正在使用要求你以 `await` 語法呼叫的第三方函式庫，例如：

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

然後，使用 `async def` 宣告你的*路徑操作函式*：


```Python hl_lines="2"
@app.get('/')