}

        @Test
        @DisplayName("Should get server")
        void testGetServer() {
            String server = "server.example.com";

            // Test with mock
            when(mockReferralData.getServer()).thenReturn(server);
            assertEquals(server, mockReferralData.getServer());
            verify(mockReferralData, times(1)).getServer();

    </proxy>
    -->
  </proxies>

  <!-- servers
   | This is a list of authentication profiles, keyed by the server-id used within the system.
   | Authentication profiles can be used whenever maven must make a connection to a remote server.
   |-->
  <servers>
    <!-- server
     | Specifies the authentication information to use when connecting to a particular server, identified by

ねらいどおりです。✔️

これは、FastAPI が `root_path` を使って、OpenAPI の既定の `server` を `root_path` の URL で生成するためです。

## 追加のサーバー { #additional-servers }

/// warning | 注意

これは高度なユースケースです。読み飛ばしても構いません。

///

既定では、**FastAPI** は OpenAPI スキーマ内に `root_path` の URL を持つ `server` を作成します。

しかし、ステージングと本番の両方と同じドキュメント UI で対話させたい場合など、別の `servers` を指定することもできます。

完全符合我们的预期。✔️

这是因为 FastAPI 使用该 `root_path` 在 OpenAPI 中创建默认的 `server`，其 URL 来自 `root_path`。

## 附加的服务器 { #additional-servers }

/// warning | 警告

这是一个更高级的用例，可以跳过。

///

默认情况下，**FastAPI** 会在 OpenAPI 模式中使用 `root_path` 的 URL 创建一个 `server`。

但你也可以提供其他备选的 `servers`，例如你希望让“同一个”文档界面同时与预发布环境和生产环境交互。

如果你传入了自定义的 `servers` 列表，并且存在 `root_path`（因为你的 API 位于代理后面），**FastAPI** 会在列表开头插入一个使用该 `root_path` 的“server”。

        .build(),
    )
    server.enqueue(
      MockResponse
        .Builder()
        .body("B")
        .build(),
    )
    assertThat(get(server.url("/a")).body.string()).isEqualTo("A")
    assertThat(get(server.url("/a")).body.string()).isEqualTo("A")
    assertThat(get(server.url("/b")).body.string()).isEqualTo("B")
    val c0e0 = server.takeRequest()

	"runtime"
	"strconv"
	"sync/atomic"
	"testing"
	"time"

	"github.com/minio/minio/internal/logger/target/testlogger"
)

func BenchmarkRequests(b *testing.B) {
	for n := 2; n <= 32; n *= 2 {
		b.Run("servers="+strconv.Itoa(n), func(b *testing.B) {
			benchmarkGridRequests(b, n)
		})
	}
}

func benchmarkGridRequests(b *testing.B, n int) {
	defer testlogger.T.SetErrorTB(b)()
	errFatal := func(err error) {

# MinIO Monitoring Guide

MinIO server exposes monitoring data over endpoints. Monitoring tools can pick the data from these endpoints. This document lists the monitoring endpoints and relevant documentation.

## Healthcheck Probe

MinIO server has two healthcheck related un-authenticated endpoints, a liveness probe to indicate if server is responding, cluster probe to check if server can be taken down for maintenance.

	"${MINIO[@]}" --address ":$start_port" "${WORK_DIR}/cicd-corpus/disk{1...5}" >"${WORK_DIR}/server1.log" 2>&1 &
	pid=$!
	disown $pid
	sleep 5

	if ! ps -p ${pid} 1>&2 >/dev/null; then
		echo "server1 log:"
		cat "${WORK_DIR}/server1.log"
		echo "FAILED"
		purge "$WORK_DIR"
		exit 1
	fi

	"${WORK_DIR}/mc" stat minio/bucket/testobj

	pkill minio
	sleep 3
}

     * specified for this filter. The wildcard has no influence on this
     * method as the server should have performed that filtering already. The
     * attributes are asserted here only because server file systems may not
     * support filtering by all attributes (e.g. even though ATTR_DIRECTORY was
     * specified the server may still return objects that are not directories).
     */
    @Override

 * clustered file server environments.
 */
public enum WitnessServiceType {
    /**
     * Cluster-aware witness service for general cluster resources
     */
    CLUSTER_WITNESS,

    /**
     * Individual file server witness for standalone servers
     */
    FILE_SERVER_WITNESS,

    /**
     * Scale-out file server witness for scale-out deployments
     */