- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for declared (0.23 sec)
-
doc/go_spec.html
Every identifier in a program must be declared. No identifier may be declared twice in the same block, and no identifier may be declared in both the file and package block. </p> <p> The <a href="#Blank_identifier">blank identifier</a> may be used like any other identifier in a declaration, but it does not introduce a binding and thus is not declared.
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu May 02 22:43:51 GMT 2024 - 279.6K bytes - Viewed (0) -
ChangeLog.md
- [`KT-57954`](https://youtrack.jetbrains.com/issue/KT-57954) K2. Auto-generated "entries" member of enum class has higher priority than user-declared companion object with same name when language version is set to 2.0
Plain Text - Registered: Fri May 03 08:18:13 GMT 2024 - Last Modified: Thu Dec 21 17:48:12 GMT 2023 - 268.7K bytes - Viewed (1) -
docs/en/docs/release-notes.md
* This is useful while calling external services, performing costly computation, etc. * This also means that if a dependency was declared as a *path operation decorator* dependency, possibly at the router level (with `.include_router()`) and then it is declared again in a specific *path operation*, the dependency will be called only once.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri May 03 23:25:42 GMT 2024 - 388.1K bytes - Viewed (1) -
CHANGELOG/CHANGELOG-1.29.md
- Fixed a situation when, sometimes, the scheduler incorrectly placed a pod in the `unschedulable` queue instead of the `backoff` queue. This happened when some plugin previously declared the pod as `unschedulable` and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the `active` queue. ([#120334](https://github.com/kubernetes/kubernetes/pull/120334), [@pohly](https://github.com/pohly))...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Apr 16 21:41:06 GMT 2024 - 299.9K bytes - Viewed (1) -
common-protos/k8s.io/api/core/v1/generated.proto
// List of addresses reachable to the node. // Queried from cloud provider, if available. // More info: https://kubernetes.io/docs/concepts/nodes/node/#addresses // Note: This field is declared as mergeable, but the merge key is not sufficiently // unique, which can cause data corruption when it is merged. Callers should instead // use a full-replacement patch. See https://pr.k8s.io/79391 for an example.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 255.8K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.28.md
- Sometimes, the scheduler incorrectly placed a pod in the "unschedulable" queue instead of the "backoff" queue. This happened when some plugin previously declared the pod as "unschedulable" and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the "active" queue. ([#120334](https://github.com/kubernetes/kubernetes/pull/120334), [@pohly](https://github.com/pohly))...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Apr 16 20:44:48 GMT 2024 - 385.1K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.27.md
- Sometimes, the scheduler incorrectly placed a pod in the "unschedulable" queue instead of the "backoff" queue. This happened when some plugin previously declared the pod as "unschedulable" and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the "active" queue. ([#120334](https://github.com/kubernetes/kubernetes/pull/120334), [@pohly](https://github.com/pohly))...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Apr 16 15:20:21 GMT 2024 - 434.3K bytes - Viewed (3) -
CHANGELOG/CHANGELOG-1.26.md
- Sometimes, the scheduler incorrectly placed a pod in the "unschedulable" queue instead of the "backoff" queue. This happened when some plugin previously declared the pod as "unschedulable" and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the "active" queue. ([#120334](https://github.com/kubernetes/kubernetes/pull/120334), [@pohly](https://github.com/pohly))...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Thu Mar 14 16:24:51 GMT 2024 - 425.7K bytes - Viewed (0)