*   ... // Handle the failure.
 *   }
 * });
 * ```
 *
 * These examples will not work if you're consuming the response body on another thread. In such
 * cases the consuming thread must call [close] when it has finished reading the response
 * body.
 *
 * ### The response body can be consumed only once.
 *
 * This class may be used to stream very large responses. For example, it is possible to use this

}

// Target - Kafka target.
type Target struct {
	status int32

	totalMessages  int64
	failedMessages int64

	wg sync.WaitGroup

	// Channel of log entries.
	// Reading logCh must hold read lock on logChMu (to avoid read race)
	// Sending a value on logCh must hold read lock on logChMu (to avoid closing)
	logCh   chan any
	logChMu sync.RWMutex

* **Intuitive**: Great editor support. <abbr title="also known as auto-complete, autocompletion, IntelliSense">Completion</abbr> everywhere. Less time debugging.
* **Easy**: Designed to be easy to use and learn. Less time reading docs.
* **Short**: Minimize code duplication. Multiple features from each parameter declaration. Fewer bugs.
* **Robust**: Get production-ready code. With automatic interactive documentation.

  }

  /**
   * Read 100 MiB of 'a' chars. This was really slow due to a performance bug in [MultipartReader],
   * and will be really slow if we regress the fix for that.
   */
  @Test
  fun `reading a large part with small byteCount`() {
    val multipartBody =
      MultipartBody
        .Builder("foo")
        .addPart(
          headersOf("header-name", "header-value"),
          object : RequestBody() {

   ({{{./xref/org/apache/maven/model/validation/DefaultModelValidator.html}source}})

   []

 * phase 2, with optional plugin processing

   ** Build up a raw model by re-reading the file and enriching it based on information available in the reactor. Some features:

      *** Resolve version of versionless parents based on relativePath (including ci-friendly versions)

     * must be between 1 and [Integer.MAX_VALUE] when converted to milliseconds.
     *
     * The call timeout spans the entire call: resolving DNS, connecting, writing the request body,
     * server processing, and reading the response body. If the call requires redirects or retries
     * all must complete within one timeout period.
     *
     * The default value is 0 which imposes no timeout.
     */
    fun callTimeout(

        setupCountField.setAccessible(true);
        assertEquals(128, setupCountField.get(response));
    }

    @Test
    @DisplayName("Test reading from different buffer positions")
    void testReadFromDifferentPositions() throws Exception {
        byte[] buffer = new byte[200];

        // Test at various positions in the buffer

      LockFreeBitArray dataArray = new LockFreeBitArray(Math.multiplyExact(dataLength, 64L));
      for (int i = 0; i < dataLength; i++) {
        dataArray.putData(i, din.readLong());
      }

      return new BloomFilter<>(dataArray, numHashFunctions, funnel, strategy);
    } catch (IOException e) {
      throw e;
    } catch (Exception e) { // sneaky checked exception

## 上下文管理器

### 什么是"上下文管理器"

"上下文管理器"是你可以在 `with` 语句中使用的任何Python对象。

例如，<a href="https://docs.python.org/zh-cn/3/tutorial/inputoutput.html#reading-and-writing-files" class="external-link" target="_blank">你可以使用`with`读取文件</a>：

```Python
with open("./somefile.txt") as f:
    contents = f.read()
    print(contents)
```

That's why in this example we have to declare it in the `response_model` parameter.

...but continue reading below to see how to overcome that.

## Return Type and Data Filtering { #return-type-and-data-filtering }