<img src="/img/tutorial/response-status-code/image01.png">

!!! note "Примечание"
    Некоторые коды статуса ответа (см. следующий раздел) указывают на то, что ответ не имеет тела.

    FastAPI знает об этом и создаст документацию OpenAPI, в которой будет указано, что тело ответа отсутствует.

## Об HTTP кодах статуса ответа

!!! note "Примечание"

astunparse == 1.6.3
dill == 0.3.7
astor == 0.7.1
typing_extensions == 4.8.0
gast == 0.4.0
termcolor == 2.3.0
wrapt == 1.16.0
tblib == 2.0.0

# Install tensorboard, and keras
# Note that here we want the latest version that matches TF major.minor version
# Note that we must use nightly here as these are used in nightly jobs
# For release jobs, we will pin these on the release branch
keras-nightly ~= 3.0.0.dev
tb-nightly ~= 2.17.0.a

<img src="/img/tutorial/response-status-code/image01.png">

!!! note "Hinweis"
    Einige Responsecodes (siehe nächster Abschnitt) kennzeichnen, dass die Response keinen Body hat.

    FastAPI versteht das und wird in der OpenAPI-Dokumentation anzeigen, dass es keinen Responsebody gibt.

## Über HTTP-Statuscodes

!!! note "Hinweis"

<img src="/img/tutorial/response-status-code/image01.png">

!!! note "Nota"
    Alguns códigos de resposta (consulte a próxima seção) indicam que a resposta não possui um corpo.

    O FastAPI sabe disso e produzirá documentos OpenAPI informando que não há corpo de resposta.

## Sobre os códigos de status HTTP

!!! note "Nota"
    Se você já sabe o que são códigos de status HTTP, pule para a próxima seção.

它可以：

* 在响应中返回状态码
* 在 OpenAPI 概图（及用户界面）中存档：

<img src="/img/tutorial/response-status-code/image01.png">

!!! note "笔记"

    某些响应状态码表示响应没有响应体（参阅下一章）。

    FastAPI 可以进行识别，并生成表明无响应体的 OpenAPI 文档。

## 关于 HTTP 状态码

!!! note "笔记"

    如果已经了解 HTTP 状态码，请跳到下一章。

在 HTTP 协议中，发送 3 位数的数字状态码是响应的一部分。

这些状态码都具有便于识别的关联名称，但是重要的还是数字。

简言之：

!!! note
    Notice that as we communicate with the database using `await`, the *path operation function* is declared with `async`.

### About `{**note.dict(), "id": last_record_id}`

`note` is a Pydantic `Note` object.

`note.dict()` returns a `dict` with its data, something like:

```Python
{
    "text": "Some note",
    "completed": False,
}
```

### 🔃 `{**note.dict(), "id": last_record_id}`

`note` Pydantic `Note` 🎚.

`note.dict()` 📨 `dict` ⏮️ 🚮 💽, 🕳 💖:

```Python
{
    "text": "Some note",
    "completed": False,
}
```

✋️ ⚫️ 🚫 ✔️ `id` 🏑.

👥 ✍ 🆕 `dict`, 👈 🔌 🔑-💲 👫 ⚪️➡️ `note.dict()` ⏮️:

```Python
{**note.dict()}
```

#
#   You will need the NVIDIA Container Toolkit for GPU testing:
#   https://github.com/NVIDIA/nvidia-container-toolkit
#
#   Note: if you interrupt a bazel command on docker (ctrl-c), you
#   will need to run `docker exec tf pkill bazel` to quit bazel.
#
#   Note: new files created from the container are owned by "root".
#   You can run e.g. `docker exec tf chown -R $(id -u):$(id -g) build_output`

pkg syscall (darwin-arm64), const NOTE_LINK = 16
pkg syscall (darwin-arm64), const NOTE_LINK ideal-int
pkg syscall (darwin-arm64), const NOTE_LOWAT = 1
pkg syscall (darwin-arm64), const NOTE_LOWAT ideal-int
pkg syscall (darwin-arm64), const NOTE_NONE = 128
pkg syscall (darwin-arm64), const NOTE_NONE ideal-int
pkg syscall (darwin-arm64), const NOTE_NSECONDS = 4

```sh
export MINIO_ROOT_USER=<ACCESS_KEY>
export MINIO_ROOT_PASSWORD=<SECRET_KEY>
minio server http://host{1...n}/export{1...m}
```

> **NOTE:** In above example `n` and `m` represent positive integers, _do not copy paste and expect it work make the changes according to local deployment and setup_.