- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 218 for handlers (0.15 sec)
-
maven-core/src/site/apt/artifact-handlers.apt
~~ specific language governing permissions and limitations ~~ under the License. --- Legacy Artifact Handlers Reference --- Hervé Boutemy --- 2013-08-02 --- Legacy Artifact Handlers Reference Maven 3 artifact handlers (see {{{../maven-artifact/apidocs/org/apache/maven/artifact/handler/ArtifactHandler.html} API}})
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Apr 23 06:12:44 GMT 2024 - 4.6K bytes - Viewed (0) -
internal/grid/README.md
## Handlers & Routes Handlers have a predefined Handler ID. In addition, there can be several *static* subroutes used to differentiate between different handlers of the same ID. A subroute on a client must match a subroute on the server. So routes cannot be used for dynamic routing, unlike HTTP.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 9.4K bytes - Viewed (0) -
docs/en/docs/tutorial/handling-errors.md
## Override the default exception handlers **FastAPI** has some default exception handlers. These handlers are in charge of returning the default JSON responses when you `raise` an `HTTPException` and when the request has invalid data. You can override these exception handlers with your own. ### Override request validation exceptions
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/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) -
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/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) -
architecture/networking/controllers.md
Construction should create informers (via `kclient.New`), setup a queue (via `controllers.NewQueue`), and register event handlers on the informers. Often, these handlers are adding something to the queue like `client.AddEventHandler(controllers.ObjectHandler(queue.AddObject))`. Construction should NOT actually start running all of these things, do I/O, or block in anyway.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Feb 09 17:41:25 GMT 2024 - 4.9K bytes - Viewed (0) -
docs/en/docs/tutorial/dependencies/dependencies-with-yield.md
This was changed in version 0.110.0 to fix unhandled memory consumption from forwarded exceptions without a handler (internal server errors), and to make it consistent with the behavior of regular Python code.
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) -
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) -
common-protos/k8s.io/api/node/v1alpha1/generated.proto
// 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 - 5K bytes - Viewed (0)