Hooks Sample Clauses

Hooks. Meter point at Hooks dist. sub (DS0905) tapped off Bann to New Boston 69 kV circuit. EMS-06. DeKalb: Meter point at DeKalb dist. sub (DS0937) tapped off New Boston to Mt. Pleasant 69 kV circuit. EMS-06. Lone Star/Bond: ▇▇▇▇▇ ▇▇▇▇' Lone Star and Bond substations are metered separately. Tap off the ▇▇▇▇▇▇ Springs to Lone Star South circuit. EMS-07. Redlick: Tap off Bann to Sugar Hill to ▇▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇▇▇. ▇▇▇-▇▇. ▇▇▇▇▇▇▇: Tap off Daingerfield to ▇▇▇▇▇▇ Springs to Lone Star Power Plant circuit. EMS-07. Adora: Tap off West Mt. Pleasant to Winsboro circuit. TS0089. EMS-08. ▇▇▇▇ City & ▇▇▇▇▇▇▇▇ Creek: Both delivery points are taps off the North New Boston to ▇▇▇▇▇▇ circuit. TS0085 & TS0092. EMS-06. Red Springs: Tap off Bann to IPC Domino circuit. TS0283. EMS-05.

Hooks. There are two hooks available, a required exec hook and an optional after hook. Hooks can either be mounted into containers using volumes or written into an image in a Dockerfile by extending the base image and specifying the correct environment variables. The base image ships with an ‘exec’ hook built-in, which the script will fallback to if no exec hook is explicitly specified. This script will be executed for each request with a number of parameters passed through. An environment variable should be set and point to where you have located your exec script. If this is not specified, it will default to app/hooks/exec, which is the built-in exec script. By default, the image processes requests synchronously and provides a response when the entire sequence of events has completed (as described in the basic request response). The client can make an asynchronous request by specifying the Prefer header in the request as per RFC7240: Prefer: respond-async The container can then decide whether to behave asynchronously or synchronously. The base image ships with an optional, built-in publishing mechanism that can be configured using the PUBLISH_ENDPOINT environment variable. This allows you specify at deployment time where you would all classification results and errors to be published to. This is achieved via a POST request with the output of exec as the body of the request to the endpoint specified in PUBLISH_ENDPOINT. You can also specify in the request a callback webhook with the X-Callback-URL header set to your webhook endpoint when you make a classification request.

Hooks. Hook latches, if used, for proper operation

Hooks. 5.31.05 Floats 5.31.06 Weights, leads 5.31.07 Fish feed, lures 5.31.10 Clothing and footwear for fishing 5.31.15 Camping equipment for fishing 5.31.20 Other equipment and accessories for fishing 5.32 FISHING TROPHIES 5.33 FISHING TOURISM 5.34 * 5.35 FISH FARMING 5.20.01 Food for dogs 5.20.02 Accessories for cinology 5.40.01 Engraving products 5.40.02 Trophies, awards 5.40.05 Hunting jewelry 5.40.06 Artworks, paintings