Then you can try and help them solve those questions.

## Ask Questions { #ask-questions }

You can [create a new question](https://github.com/fastapi/fastapi/discussions/new?category=questions) in the GitHub repository, for example to:

* Ask a **question** or ask about a **problem**.
* Suggest a new **feature**.

**Note**: if you do it, then I'm going to ask you to also help others. 😉

Try to be as specific and objective as possible, avoid generalizations.

For conversations that are more difficult, for example to reject a PR, you can ask me (@tiangolo) to handle it directly.

## Edit PR Titles

* Edit the PR title to start with an emoji from [gitmoji](https://gitmoji.dev/).

	}

	// We have 2 cases:
	// 1) Cold listing, just list.
	// 2) Returning, but with no id. Start async listing.
	// 3) Returning, with ID, stream from list.
	//
	// If we don't have a list id we must ask the server if it has a cache or create a new.
	if o.ID != "" && !o.Transient {
		// Create or ping with handout...
		rpc := globalNotificationSys.restClientFromHash(pathJoin(o.Bucket, o.Prefix))
		var c *metacache

  If var_name has been set as environment variable, use the preset value, else
  ask for user input. If no input is provided, the default is used.

  Args:
    environ_cp: copy of the os.environ.
    var_name: string for name of environment variable, e.g. "TF_NEED_CUDA".
    ask_for_var: string for how to ask for user input.
    var_default: default value string.

  Returns:
    string value for var_name

* For user-facing features, what will the API look like?
* What test cases should it have? What could go wrong?
* How will it roughly be implemented? We'll happily provide code pointers to save you time.

We may ask you to answer these questions directly in the GitHub issue or (for large changes) in a shared Google Doc.

### 해결책 제안하기 { #suggest-solutions }

* 질문을 충분히 이해한 후에는 가능한 **답변**을 제공할 수 있습니다.

* 많은 경우, 질문자의 **근본적인 문제나 사용 사례**를 이해하는 것이 더 좋습니다. 그들이 시도하는 방법보다 더 나은 해결책이 있을 수 있기 때문입니다.

### 종료 요청하기 { #ask-to-close }

질문자가 답변을 하면, 여러분이 문제를 해결했을 가능성이 높습니다. 축하합니다, **여러분은 영웅입니다**! 🦸

* 이제 문제를 해결했다면, 질문자에게 다음을 요청할 수 있습니다.

    * GitHub Discussions에서: 댓글을 **답변**으로 표시하도록 요청하세요.

4. Submit a pull request

          currentTask = coordinatorTask
          taskRunner.notifyAll()
        }
      }

    // Let the coordinator process its interruption.
    runTasks()
  }

  /** Ask a single task to proceed. Used by the test thread only. */
  fun runNextTask() {
    taskRunner.assertLockNotHeld()

    taskRunner.withLock {
      val contextSwitchCountBefore = contextSwitchCount

* 如果你非常热心，你也可以尝试仅根据问题描述自己**构造一个示例**。不过要记住，这可能会花很多时间，通常先请他们澄清问题会更好。

### 提出解决方案 { #suggest-solutions }

* 在能够理解问题之后，你可以给出一个可能的**答案**。

* 很多情况下，更好的是去理解他们**底层的问题或场景**，因为可能存在比他们尝试的方法更好的解决方式。

### 请求关闭问题 { #ask-to-close }

如果他们回复了，很有可能你已经解决了他们的问题，恭喜，**你是英雄**！🦸

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

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

* 如果你有心力，你也可以嘗試自己**建立一個範例**，僅依據問題描述來還原。不過請記得這可能很耗時，或許更好的是先請他們把問題說清楚。

### 提出解法建議 { #suggest-solutions }

* 在能夠理解問題後，你可以給出可能的**答案**。

* 很多時候，最好能理解他們的**底層問題或使用情境**，因為可能有比他們嘗試的方法更好的解決之道。

### 請求關閉議題 { #ask-to-close }

如果他們回覆了，你很可能已經解決了他們的問題，恭喜，**你是英雄**！🦸

* 現在，如果問題已解決，你可以請他們：
    * 在 GitHub Discussions：把某則留言標記為**答案**。
    * 在 GitHub Issues：**關閉**該 issue。

## 追蹤 GitHub 儲存庫 { #watch-the-github-repository }