Please be considerate of your servers and their operators as you roll out this release. Compression
saves bandwidth but it costs CPU and memory! If you run into a problem you may need to adjust or
disable the `permessage-deflate` compression settings on your server.

Note that OkHttp won't use compression when sending messages smaller than 1 KiB.

 *  Fix: Don't crash when the URL hostname contains an underscore on Android.

    ):
        fields_to_extract = get_cached_model_fields(first_field.field_info.annotation)
        single_not_embedded_field = True
        # If headers are in a Pydantic model, the way to disable convert_underscores
        # would be with Header(convert_underscores=False) at the Pydantic model level
        default_convert_underscores = getattr(
            first_field.field_info, "convert_underscores", True

/// note | 技术细节

OpenAPI 规范中的 `servers` 属性是可选的。

如果你没有指定 `servers` 参数，并且 `root_path` 等于 `/`，则默认情况下，生成的 OpenAPI 模式中会完全省略 `servers` 属性，这等价于只有一个 `url` 值为 `/` 的服务器。

///

### 从 `root_path` 禁用自动服务器 { #disable-automatic-server-from-root-path }

如果你不希望 **FastAPI** 包含一个使用 `root_path` 的自动服务器，可以使用参数 `root_path_in_servers=False`：

{* ../../docs_src/behind_a_proxy/tutorial004_py310.py hl[9] *}

这样它就不会被包含到 OpenAPI 模式中。

// Enables only graph collection in RunMetadata on the functions executed from
// this context.
TF_CAPI_EXPORT extern void TFE_ContextEnableGraphCollection(TFE_Context* ctx);

// Disables only graph collection in RunMetadata on the functions executed from
// this context.
TF_CAPI_EXPORT extern void TFE_ContextDisableGraphCollection(TFE_Context* ctx);

{* ../../docs_src/response_model/tutorial003_04_py310.py hl[8] *}

...這會失敗，因為該型別註解不是 Pydantic 型別，且它也不只是一個單一的 `Response` 類別或其子類別，而是 `Response` 與 `dict` 的聯集（兩者任一）。

### 停用回應模型 { #disable-response-model }

延續上面的例子，你可能不想要 FastAPI 執行預設的資料驗證、文件化、過濾等動作。

但你可能仍想在函式上保留回傳型別註解，以獲得編輯器與型別檢查工具（例如 mypy）的支援。

這種情況下，你可以設定 `response_model=None` 來停用回應模型的產生：

   * comes up in practice (maybe through some kind of sanitizer-like testing that intentionally
   * inflicts spurious interrupts on us?), we might have to accept some flakiness or disable some
   * tests, at least under whichever environment (JRE or Android) we see such problems.
   */

  @SuppressWarnings("WaitNotInLoop") // see comment above
  public void testConditionAwaitTimeoutExceeded() {

OpenAPI 仕様の `servers` プロパティは任意です。

`servers` パラメータを指定せず、かつ `root_path` が `/` の場合、生成される OpenAPI スキーマからは `servers` プロパティが既定で完全に省略されます。これは、`url` が `/` の server が 1 つあるのと同等です。

///

### `root_path` 由来の自動 server を無効化 { #disable-automatic-server-from-root-path }

`root_path` を用いた自動的な server を **FastAPI** に含めてほしくない場合は、パラメータ `root_path_in_servers=False` を使用します:

{* ../../docs_src/behind_a_proxy/tutorial004_py310.py hl[9] *}

		return f, nil
	}

	f, err := parser.ParseFile(fset, filename, nil, parser.ParseComments)
	if err != nil {
		return nil, err
	}
	parsedFileCache[filename] = f

	return f, nil
}

// Disable before debugging non-obvious errors from the type-checker.
const usePkgCache = true

var (
	pkgCache = map[string]*apiPackage{} // map tagKey to package

allowing a racing thread to read 1 as well.
</p>

<p>
Note that all these optimizations are permitted in C/C++ compilers:
a Go compiler sharing a back end with a C/C++ compiler must take care
to disable optimizations that are invalid for Go.
</p>

<p>
Note that the prohibition on introducing data races
does not apply if the compiler can prove that the races
do not affect correct execution on the target platform.

     */
    public boolean isUseSession() {
        return useSession;
    }

    /**
     * Sets whether to use HTTP sessions.
     *
     * @param useSession true to enable sessions, false to disable
     */
    public void setUseSession(final boolean useSession) {
        this.useSession = useSession;
    }

    /**
     * Adds an initial facet parameter mapping.
     *