- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 1,907 for Your (0.11 sec)
-
README.md
```gradle dependencies { // Pick one: // 1. Use Guava in your implementation only: implementation("com.google.guava:guava:33.4.8-jre") // 2. Use Guava types in your public API: api("com.google.guava:guava:33.4.8-jre") // 3. Android - Use Guava in your implementation only: implementation("com.google.guava:guava:33.4.8-android") // 4. Android - Use Guava types in your public API: api("com.google.guava:guava:33.4.8-android")
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Tue Aug 05 15:30:14 UTC 2025 - 6.2K bytes - Viewed (0) -
CONTRIBUTING.md
- To run `make test` and `make build` completes. ### Commit changes After verification, commit your changes. This is a [great post](https://chris.beams.io/posts/git-commit/) on how to write useful commit messages ``` git commit -am 'Add some feature' ``` ### Push to the branch Push your locally committed changes to the remote origin (your fork) ```
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Mon Aug 05 18:35:53 UTC 2024 - 2.9K bytes - Viewed (0) -
docs/en/docs/tutorial/security/simple-oauth2.md
After authenticating in the system, you will see it like: <img src="/img/tutorial/security/image05.png"> ### Get your own user data { #get-your-own-user-data } Now use the operation `GET` with the path `/users/me`. You will get your user's data, like: ```JSON { "username": "johndoe", "email": "******@****.***", "full_name": "John Doe", "disabled": false,
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 9.4K bytes - Viewed (0) -
docs/en/docs/deployment/versions.md
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 3.5K bytes - Viewed (0) -
docs/en/docs/tutorial/security/first-steps.md
Because we are using a relative URL, if your API was located at `https://example.com/`, then it would refer to `https://example.com/token`. But if your API was located at `https://example.com/api/v1/`, then it would refer to `https://example.com/api/v1/token`.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 8.4K bytes - Viewed (0) -
docs/en/docs/tutorial/debugging.md
/// ## Run your code with your debugger { #run-your-code-with-your-debugger } Because you are running the Uvicorn server directly from your code, you can call your Python program (your FastAPI application) directly from the debugger. --- For example, in Visual Studio Code, you can: * Go to the "Debug" panel.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 2.5K bytes - Viewed (0) -
docs/en/docs/deployment/concepts.md
### Server Memory { #server-memory } For example, if your code loads a Machine Learning model with **1 GB in size**, when you run one process with your API, it will consume at least 1 GB of RAM. And if you start **4 processes** (4 workers), each will consume 1 GB of RAM. So in total, your API will consume **4 GB of RAM**.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 18.6K bytes - Viewed (0) -
CONTRIBUTING.md
If you have improvements to TensorFlow, send us your pull requests! For those just getting started, GitHub has a [how-to](https://help.github.com/articles/using-pull-requests/). TensorFlow team members will be assigned to review your pull requests. Once the pull requests are approved and pass continuous integration checks, a TensorFlow team member will apply `ready to pull` label to your change. This means we are
Registered: Tue Sep 09 12:39:10 UTC 2025 - Last Modified: Sat Jan 11 04:47:59 UTC 2025 - 15.9K bytes - Viewed (0) -
docs/en/docs/advanced/async-tests.md
You have already seen how to test your **FastAPI** applications using the provided `TestClient`. Up to now, you have only seen how to write synchronous tests, without using `async` functions.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 3.9K bytes - Viewed (0) -
docs/en/docs/tutorial/response-model.md
FastAPI will use this return type to: * **Validate** the returned data. * If the data is invalid (e.g. you are missing a field), it means that *your* app code is broken, not returning what it should, and it will return a server error instead of returning incorrect data. This way you and your clients can be certain that they will receive the data and the data shape expected. * Add a **JSON Schema** for the response, in the OpenAPI *path operation*.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 16K bytes - Viewed (0)