- Sort Score
- Result 10 results
- Languages All
Results 41 - 50 of 1,265 for operation (0.15 sec)
-
internal/dsync/locker.go
// * a boolean to indicate success/failure of the operation // * an error on failure of lock request operation. RLock(ctx context.Context, args LockArgs) (bool, error) // Do write lock for given LockArgs. It should return // * a boolean to indicate success/failure of the operation // * an error on failure of lock request operation. Lock(ctx context.Context, args LockArgs) (bool, error)
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Tue Jan 18 20:44:38 UTC 2022 - 2.7K bytes - Viewed (0) -
docs/en/docs/tutorial/bigger-applications.md
And we can add a list of `dependencies` that will be added to all the *path operations* in the router and will be executed/solved for each request made to them. /// tip
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 18.4K bytes - Viewed (0) -
docs/en/docs/tutorial/background-tasks.md
In this case, the task function will write to a file (simulating sending an email). And as the write operation doesn't use `async` and `await`, we define the function with normal `def`: {* ../../docs_src/background_tasks/tutorial001.py hl[6:9] *} ## Add the background task Inside of your *path operation function*, pass your task function to the *background tasks* object with the method `.add_task()`:
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 27 15:22:48 UTC 2024 - 4.8K bytes - Viewed (0) -
docs/de/docs/advanced/generate-clients.md
... das liegt daran, dass der Client-Generator für jede *Pfadoperation* die OpenAPI-interne **Operation-ID** verwendet. OpenAPI erfordert, dass jede Operation-ID innerhalb aller *Pfadoperationen* eindeutig ist. Daher verwendet FastAPI den **Funktionsnamen**, den **Pfad** und die **HTTP-Methode/-Operation**, um diese Operation-ID zu generieren. Denn so kann sichergestellt werden, dass die Operation-IDs eindeutig sind.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 11.9K bytes - Viewed (0) -
tensorflow/c/eager/c_api.h
// This function will block till the operation that produces `h` has completed. TF_CAPI_EXPORT extern int64_t TFE_TensorHandleDim(TFE_TensorHandle* h, int dim_index, TF_Status* status); // Returns the device of the operation that produced `h`. If `h` was produced by
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Thu Apr 27 21:07:00 UTC 2023 - 22.8K bytes - Viewed (0) -
docs/fr/docs/tutorial/first-steps.md
Voici notre "**fonction de chemin**" (ou fonction d'opération de chemin) : * **chemin** : `/`. * **opération** : `get`. * **fonction** : la fonction sous le "décorateur" (sous `@app.get("/")`). ```Python hl_lines="7" {!../../docs_src/first_steps/tutorial001.py!} ``` C'est une fonction Python. Elle sera appelée par **FastAPI** quand une requête sur l'URL `/` sera reçue via une opération `GET`.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 10.3K bytes - Viewed (0) -
docs/en/docs/tutorial/dependencies/index.md
It is just a function that can take all the same parameters that a *path operation function* can take: {* ../../docs_src/dependencies/tutorial001_an_py310.py hl[8:9] *} That's it. **2 lines**. And it has the same shape and structure that all your *path operation functions* have. You can think of it as a *path operation function* without the "decorator" (without the `@app.get("/some-path")`).
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Mon Oct 28 11:18:17 UTC 2024 - 9.2K bytes - Viewed (0) -
docs/en/docs/tutorial/security/get-current-user.md
```Python hl_lines="30-32" {!> ../../docs_src/security/tutorial002.py!} ``` //// ## Recap You can now get the current user directly in your *path operation function*. We are already halfway there. We just need to add a *path operation* for the user/client to actually send the `username` and `password`.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 7.4K bytes - Viewed (0) -
guava-tests/benchmark/com/google/common/collect/StreamsBenchmark.java
@Override Object operate(Stream<?> stream) { return stream.parallel().reduce((a, b) -> b); } }; abstract Object operate(Stream<?> stream); } @Param private Operation operation; Collection<Object> collection; @BeforeExperiment void setUp() { collection = source.supplier.get(); for (int i = 0; i < size; i++) { collection.add(new Object()); } }
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Fri Oct 18 20:24:49 UTC 2024 - 2.8K bytes - Viewed (0) -
docs/de/docs/tutorial/first-steps.md
Ein „Pfad“ wird häufig auch als „Endpunkt“ oder „Route“ bezeichnet. /// Bei der Erstellung einer API ist der „Pfad“ die wichtigste Möglichkeit zur Trennung von „Anliegen“ und „Ressourcen“. #### Operation „Operation“ bezieht sich hier auf eine der HTTP-„Methoden“. Eine von diesen: * `POST` * `GET` * `PUT` * `DELETE` ... und die etwas Exotischeren: * `OPTIONS` * `HEAD` * `PATCH`
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 10.5K bytes - Viewed (0)