<div class="termy">

```console
$ fastapi deploy

Deploying to FastAPI Cloud...

✅ Deployment successful!

🐔 Ready the chicken! Your app is ready at https://myapp.fastapicloud.dev
```

</div>

Das war’s! Jetzt können Sie unter dieser URL auf Ihre App zugreifen. ✨

#### Über FastAPI Cloud { #about-fastapi-cloud }

    expectedEvents += ConnectionAcquired::class
    expectedEvents += RequestHeadersStart::class
    expectedEvents += RequestHeadersEnd::class
    expectedEvents += RequestBodyStart::class
    // ... but we can read the response even after writing the request fails.
    expectedEvents += RequestFailed::class
    expectedEvents += ResponseHeadersStart::class
    expectedEvents += ResponseHeadersEnd::class

                        request.getLocalRepository().getBasedir(),
                        request.getLocalRepository().pathOf(pomArtifact));

                try {
                    Model model = modelReader.read(pomFile, null).getDelegate();

                    dependencies = Dependency.dependencyToApiV3(model.getDependencies());
                } catch (IOException e) {
                    e.printStackTrace();
                }

foreach configuration element:
 - if read only and being set squawk

 - find the parameter
 - get value from expression or default
 - if required and null squawk

      <configuration>
        <attached implementation="boolean" default-value="true"/>

使用 `with` 區塊可確保在產生器函式（包含 `yield` 的函式）完成後關閉該類檔案物件，也就是在送完回應之後。

在這個範例中因為是存在記憶體的假檔案（`io.BytesIO`），影響不大；但若是實際檔案，務必在處理完成後關閉檔案。

### 檔案與 Async { #files-and-async }

多數情況下，類檔案物件預設不相容於 async/await。

例如，它們沒有 `await file.read()`，也不支援 `async for chunk in file`。

而且在許多情況下，讀取它們會是阻塞操作（可能阻塞事件迴圈），因為資料是從磁碟或網路讀取。

/// info

上面的範例其實是例外，因為 `io.BytesIO` 物件已在記憶體中，讀取不會阻塞任何東西。

但在多數情況下，讀取檔案或類檔案物件會造成阻塞。

///

            }

            try {
                try (InputStream is = getClass().getClassLoader().getResourceAsStream("jcifs/http/ne.css");) {
                    while ((n = is.read(buf)) != -1) {
                        sb.append(new String(buf, 0, n, "ISO8859_1"));
                    }
                    this.style = sb.toString();
                }
            } catch (final IOException ioe) {

*   Taint key `unreachable` is now in GA.
*   Taint key `notReady` is changed to `not-ready`, and is also now in GA.
*   These changes are automatically updated for taints. Tolerations for these taints must be updated manually. Specifically, you must:
    *   Change `node.alpha.kubernetes.io/notReady` to `node.kubernetes.io/not-ready`
    *   Change `node.alpha.kubernetes.io/unreachable` to  `node.kubernetes.io/unreachable`

    @RetainedLocalRef F localFallback = fallback;
    if ((localInputFuture == null | localExceptionType == null | localFallback == null)
        // This check, unlike all the others, is a volatile read
        || isCancelled()) {
      return;
    }
    inputFuture = null;

    // For an explanation of the cases here, see the comments on AbstractTransformFuture.run.
    V sourceResult = null;

### Arquivos e async { #files-and-async }

Na maioria dos casos, objetos semelhantes a arquivo não são compatíveis com async e await por padrão.

Por exemplo, eles não têm `await file.read()`, nem `async for chunk in file`.

E, em muitos casos, lê-los seria uma operação bloqueante (que poderia bloquear o loop de eventos), pois são lidos do disco ou da rede.

/// info | Informação

actions: # - "s3:CreateBucket" # - "s3:DeleteBucket" # - "s3:GetBucketLocation" # - "s3:ListBucket" # - "s3:ListBucketMultipartU" ## readonlyexamplepolic policy grants access to buckets with name starting with example. ## In addition, grants objects read permissions on buckets starting with example. # - name: readonlyexamplepolic # statements: # - resources: # - 'arn:aws:s3:::example*/*' # actions: # - "s3:GetObject" # - resources: # - 'arn:aws:s3:::example*' # actions: # - "s3:GetBucketLocation" #...