entry.setValueReference(oldValueRef);

    // no entry
    assertThat(segment.replace(key, hash, oldValue, newValue)).isFalse();
    assertThat(segment.count).isEqualTo(0);

    // same value
    table.set(index, entry);
    segment.count++;
    assertThat(segment.count).isEqualTo(1);
    assertThat(segment.get(key, hash)).isSameInstanceAs(oldValue);

    entry.setValueReference(oldValueRef);

    // no entry
    assertThat(segment.replace(key, hash, oldValue, newValue)).isFalse();
    assertThat(segment.count).isEqualTo(0);

    // same value
    table.set(index, entry);
    segment.count++;
    assertThat(segment.count).isEqualTo(1);
    assertThat(segment.get(key, hash)).isSameInstanceAs(oldValue);

        return facadeSelectList(createCB(cbLambda));
    }

    public PagingResultBean<AccessToken> selectPage(CBCall<AccessTokenCB> cbLambda) {
        // #pending same?
        return (PagingResultBean<AccessToken>) facadeSelectList(createCB(cbLambda));
    }

    public void selectCursor(CBCall<AccessTokenCB> cbLambda, EntityRowHandler<AccessToken> entityLambda) {

/// info

自 FastAPI `0.102.0` 起新增 `separate_input_output_schemas` 的支援。🤓

///

{* ../../docs_src/separate_openapi_schemas/tutorial002_py310.py hl[10] *}

### 文件中輸入與輸出使用相同結構描述的模型 { #same-schema-for-input-and-output-models-in-docs }

此時輸入與輸出將共用同一個模型結構描述，只有 `Item`，其中 `description` 不是必填：

<div class="screenshot">
<img src="/img/tutorial/separate-openapi-schemas/image05.png">

/// info | 信息

对 `separate_input_output_schemas` 的支持是在 FastAPI `0.102.0` 中添加的。🤓

///

{* ../../docs_src/separate_openapi_schemas/tutorial002_py310.py hl[10] *}

### 文档中输入/输出使用同一 Schema 的模型 { #same-schema-for-input-and-output-models-in-docs }

现在该模型的输入和输出将只使用一个 schema，即 `Item`，并且其中的 `description` **不是必填**：

<div class="screenshot">
<img src="/img/tutorial/separate-openapi-schemas/image05.png">

site_enabled_peer=$(./mc admin replicate info minio10)

[[ $site_enabled =~ "is not enabled" ]] && {
	echo "expected both peers to have same information"
	exit_1
}

[[ $site_enabled_peer =~ "is not enabled" ]] && {
	echo "expected both peers to have same information"
	exit_1
}

./mc admin user add minio1 foobar foo12345

## add foobar-g group with foobar
./mc admin group add minio2 foobar-g foobar

    """
    This is a special class that you can define in a parameter in a dependency to
    obtain the OAuth2 scopes required by all the dependencies in the same chain.

    This way, multiple dependencies can have different scopes, even when used in the
    same *path operation*. And with this, you can access all the scopes required in
    all those dependencies in a single place.

    Read more about it in the

            NdrBuffer encodeBuffer = mock(NdrBuffer.class);
            when(encodeBuffer.derive(anyInt())).thenReturn(encodeBuffer);
            originalUuid.encode(encodeBuffer);

            // Mock decoding buffer with the same values
            NdrBuffer decodeBuffer = mock(NdrBuffer.class);
            when(decodeBuffer.dec_ndr_long()).thenReturn(originalUuid.time_low);

     * The maven-resources-plugin resolves {@code targetPath} as:
     * {@code project.build.outputDirectory + "/" + targetPath}, which results in
     * {@code target/classes/META-INF/resources}. This method provides the same base directory
     * ({@code target/classes}) for Maven 4 API consumers.
     * </p>
     * <p>
     * <strong>Example:</strong>
     * </p>
     * <pre>{@code

| [FS](https://github.com/minio/kes/wiki/Filesystem-Keystore)                                  | Local testing or development (**Not recommended for production**) |

The MinIO-KES configuration is always the same - regardless of the underlying KMS implementation. Checkout the MinIO-KES [configuration example](https://github.com/minio/kes/wiki/MinIO-Object-Storage).

### Further references