- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 118 for Handler (0.21 sec)
-
common-protos/k8s.io/api/node/v1beta1/generated.proto
// handler specifies the underlying runtime and configuration that the CRI // implementation will use to handle pods of this class. The possible values // are specific to the node & CRI configuration. It is assumed that all // handlers are available on every node, and handlers of the same name are // equivalent on every node. // For example, a handler called "runc" might specify that the runc OCI
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 4.4K bytes - Viewed (0) -
docs/en/docs/tutorial/handling-errors.md
And it also includes a default exception handler for it. To override it, import the `RequestValidationError` and use it with `@app.exception_handler(RequestValidationError)` to decorate the exception handler. The exception handler will receive a `Request` and the exception. ```Python hl_lines="2 14-16" {!../../../docs_src/handling_errors/tutorial004.py!} ```
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 9.1K bytes - Viewed (0) -
docs/de/docs/tutorial/handling-errors.md
Sie könnten einen benutzerdefinierten Exceptionhandler mittels `@app.exception_handler()` hinzufügen: ```Python hl_lines="5-7 13-18 24" {!../../../docs_src/handling_errors/tutorial003.py!} ``` Wenn Sie nun `/unicorns/yolo` anfragen, `raise`d die *Pfadoperation* eine `UnicornException`. Aber diese wird von `unicorn_exception_handler` gehandhabt.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 20:28:29 GMT 2024 - 10.6K bytes - Viewed (0) -
docs/ru/docs/tutorial/dependencies/dependencies-with-yield.md
opt raise dep -->> handler: Raise HTTPException handler -->> client: HTTP error response dep -->> dep: Raise other exception end dep ->> operation: Run dependency, e.g. DB session opt raise operation -->> dep: Raise HTTPException dep -->> handler: Auto forward exception handler -->> client: HTTP error response
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Apr 02 04:21:06 GMT 2024 - 19.6K bytes - Viewed (0) -
docs/en/docs/tutorial/dependencies/dependencies-with-yield.md
participant client as Client participant handler as Exception handler participant dep as Dep with yield participant operation as Path Operation participant tasks as Background tasks Note over client,operation: Can raise exceptions, including HTTPException client ->> dep: Start request Note over dep: Run code up to yield opt raise Exception dep -->> handler: Raise Exception
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Feb 24 23:06:37 GMT 2024 - 14.1K bytes - Viewed (0) -
okcurl/src/main/kotlin/okhttp3/curl/logging/LoggingUtil.kt
activeLogger.level = Level.FINE handler.level = Level.FINE handler.formatter = MessageFormatter activeLogger.addHandler(handler) } if (sslDebug) { val activeLogger = getLogger("javax.net.ssl") activeLogger.level = Level.FINEST handler.level = Level.FINEST handler.formatter = MessageFormatter
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Fri Apr 05 03:30:42 GMT 2024 - 2.7K bytes - Viewed (1) -
docs/zh/docs/tutorial/dependencies/dependencies-with-yield.md
opt raise operation -->> dep: Raise HTTPException dep -->> handler: Auto forward exception handler -->> client: HTTP error response operation -->> dep: Raise other exception dep -->> handler: Auto forward exception end operation ->> client: Return response to client Note over client,operation: Response is already sent, can't change it anymore
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 10.3K bytes - Viewed (0) -
common-protos/k8s.io/api/node/v1/generated.proto
// handler specifies the underlying runtime and configuration that the CRI // implementation will use to handle pods of this class. The possible values // are specific to the node & CRI configuration. It is assumed that all // handlers are available on every node, and handlers of the same name are // equivalent on every node. // For example, a handler called "runc" might specify that the runc OCI
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 4.4K bytes - Viewed (0) -
docs/en/docs/advanced/events.md
{!../../../docs_src/events/tutorial001.py!} ``` In this case, the `startup` event handler function will initialize the items "database" (just a `dict`) with some values. You can add more than one event handler function. And your application won't start receiving requests until all the `startup` event handlers have completed. ### `shutdown` event
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 7.8K bytes - Viewed (0) -
docs/de/docs/tutorial/dependencies/dependencies-with-yield.md
client ->> dep: Startet den Request Note over dep: Führt den Code bis zum yield aus opt Löst Exception aus dep -->> handler: Löst Exception aus handler -->> client: HTTP-Error-Response end dep ->> operation: Führt Abhängigkeit aus, z. B. DB-Session opt Löst aus operation -->> dep: Löst Exception aus (z. B. HTTPException) opt Handhabt
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 18:10:29 GMT 2024 - 13.5K bytes - Viewed (0)