navigate to the
[GitHub "issues" tab](https://github.com/tensorflow/tensorflow/issues) and start
looking through interesting issues. If you are not sure of where to start, then
start by trying one of the smaller/easier issues here i.e.
[issues with the "good first issue" label](https://github.com/tensorflow/tensorflow/labels/good%20first%20issue)
and then take a look at the

    assertThat(simplifyPath("../this/../ok")).isEqualTo("../ok");
  }

  // https://github.com/google/guava/issues/705
  public void test705() {
    assertThat(simplifyPath("x/../../b")).isEqualTo("../b");
    assertThat(simplifyPath("x/../b")).isEqualTo("b");
  }

  // https://github.com/google/guava/issues/716
  public void test716() {
    assertThat(simplifyPath("./b")).isEqualTo("b");

    assertThat(simplifyPath("../this/../ok")).isEqualTo("../ok");
  }

  // https://github.com/google/guava/issues/705
  public void test705() {
    assertThat(simplifyPath("x/../../b")).isEqualTo("../b");
    assertThat(simplifyPath("x/../b")).isEqualTo("b");
  }

  // https://github.com/google/guava/issues/716
  public void test716() {
    assertThat(simplifyPath("./b")).isEqualTo("b");

These issues are more complex and might be challenging for first-time contributors.

You can share your interest in fixing the issue by commenting on it.
If somebody shared their interest in the issue, please consider letting them work on it.

  * Pod IP allocation-related issues. Deleting the docker checkpoint prior to
restarting the daemon alleviates this issue, but hasn’t been verified to
completely eliminate the IP allocation issue. More information [here](https://github.com/kubernetes/kubernetes/issues/21523#issuecomment-191498969)

[![Fuzzing Status](https://oss-fuzz-build-logs.storage.googleapis.com/badges/tensorflow.svg)](https://bugs.chromium.org/p/oss-fuzz/issues/list?sort=-opened&can=1&q=proj:tensorflow)
[![Fuzzing Status](https://oss-fuzz-build-logs.storage.googleapis.com/badges/tensorflow-py.svg)](https://bugs.chromium.org/p/oss-fuzz/issues/list?sort=-opened&can=1&q=proj:tensorflow-py)
[![OSSRank](https://shields.io/endpoint?url=https://ossrank.com/shield/44)](https://ossrank.com/p/44)

    * In GitHub Issues: **close** the issue.

## Watch the GitHub repository { #watch-the-github-repository }

You can "watch" FastAPI in GitHub (clicking the "watch" button at the top right): [https://github.com/fastapi/fastapi](https://github.com/fastapi/fastapi). 👀

    <developerConnection>scm:git:******@****.***:google/guava.git</developerConnection>
    <url>https://github.com/google/guava</url>
  </scm>
  <issueManagement>
    <system>GitHub Issues</system>
    <url>https://github.com/google/guava/issues</url>
  </issueManagement>
  <ciManagement>
    <system>GitHub Actions</system>
    <url>https://github.com/google/guava/actions</url>
  </ciManagement>
  <properties>
    <!--

  }

  /**
   * The pinner should pull the root certificate from the trust manager.
   */
  @Test
  fun pinRootNotPresentInChain() {
    // Fails on 11.0.1 https://github.com/square/okhttp/issues/4703
    val rootCa =
      HeldCertificate
        .Builder()
        .serialNumber(1L)
        .certificateAuthority(1)
        .commonName("root")
        .build()
    val intermediateCa =

* 现在，如果问题已解决，你可以请他们：
    * 在 GitHub Discussions 中：将你的评论标记为**答案**。
    * 在 GitHub Issues 中：**关闭**该 issue。

## 关注 GitHub 资源库 { #watch-the-github-repository }

你可以在 GitHub 上「关注」FastAPI（点击右上角的「watch」按钮）：[https://github.com/fastapi/fastapi](https://github.com/fastapi/fastapi)。👀

如果你选择「Watching」而非「Releases only」，当有人创建新的 issue 或问题时你会收到通知。你也可以指定只通知新 issues、discussions、PR 等。

然后你就可以尝试帮助他们解决这些问题。

## 提问 { #ask-questions }