- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for wait4 (0.33 sec)
-
src/cmd/vendor/golang.org/x/tools/internal/stdlib/manifest.go
{"WSASend", Func, 0}, {"WSASendTo", Func, 0}, {"WSASendto", Func, 0}, {"WSAStartup", Func, 0}, {"WSTOPPED", Const, 0}, {"WTRAPPED", Const, 1}, {"WUNTRACED", Const, 0}, {"Wait4", Func, 0}, {"WaitForSingleObject", Func, 0}, {"WaitStatus", Type, 0}, {"WaitStatus.ExitCode", Field, 0}, {"Win32FileAttributeData", Type, 0}, {"Win32FileAttributeData.CreationTime", Field, 0},
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Apr 02 02:20:05 UTC 2024 - 534.2K bytes - Viewed (0) -
operator/cmd/mesh/testdata/manifest-generate/output/all_on.golden-show-in-gh-pull-request.yaml
{{- else if $holdProxy }} lifecycle: postStart: exec: command: - pilot-agent - wait {{- else if $nativeSidecar }} {{- /* preStop is called when the pod starts shutdown. Initialize drain. We will get SIGTERM once applications are torn down. */}} lifecycle:
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed Jan 10 05:10:03 UTC 2024 - 506.8K bytes - Viewed (0) -
api/openapi-spec/v3/apis__apps__v1_openapi.json
"podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is `OrderedReady`, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is `Parallel` which will create pods in parallel to match the desired scale without waiting, and on scale down will delete...
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Wed May 29 22:40:29 UTC 2024 - 810.7K bytes - Viewed (0) -
RELEASE.md
* Add int64 data type support for dynamic update slice's indice tensor. * `tf.data` * Add `wait` to `tf.data.Dataset.load`. If `True`, for snapshots written with `distributed_save`, it reads the snapshot while it is being written. For snapshots written with regular `save`, it waits for the snapshot until it's finished. The default is `False` for backward compatibility. Users of
Registered: Sun Jun 16 05:45:23 UTC 2024 - Last Modified: Tue Jun 11 23:24:08 UTC 2024 - 730.3K bytes - Viewed (0) -
api/openapi-spec/v3/apis__resource.k8s.io__v1alpha2_openapi.json
"description": "If specified, the time in seconds before the operation should be retried. Some errors may indicate the client must take an alternate action - for those errors this field may indicate how long to wait before taking the alternate action.", "format": "int32", "type": "integer" }, "uid": {
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Mon Apr 22 12:18:45 UTC 2024 - 656.6K bytes - Viewed (0)