Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for _INVALID_ (0.07 sec)

  2. github.com/kubernetes/kubernetes

    pkg/kubelet/config/http_test.go 

    		},
		{
			desc: "Invalid volume name",
			pod: &v1.Pod{
				TypeMeta: metav1.TypeMeta{APIVersion: "v1"},
				Spec: v1.PodSpec{
					Volumes: []v1.Volume{{Name: "_INVALID_"}},
				},
			},
		},
		{
			desc: "Duplicate volume names",
			pod: &v1.Pod{
				TypeMeta: metav1.TypeMeta{APIVersion: "v1"},
				Spec: v1.PodSpec{
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Fri Jan 14 09:38:23 UTC 2022
    - 11.2K bytes
    - Viewed (0)
  3. github.com/gradle/gradle

    platforms/documentation/docs/src/docs/userguide/jvm/toolchains.adoc 

    A specification without a language version, in most cases, would be treated as a one that selects the toolchain of the current build.

Usage of _invalid_ instances of `JavaToolchainSpec` results in a build error since Gradle 8.0.


== Toolchains for tasks
    Registered: Wed Jun 12 18:38:38 UTC 2024
    - Last Modified: Fri Apr 26 05:37:54 UTC 2024
    - 24.8K bytes
    - Viewed (0)
  4. github.com/gradle/gradle

    platforms/documentation/docs/src/docs/userguide/releases/upgrading/upgrading_version_7.adoc 

    Starting with Gradle 7.6, toolchain specifications that configure other properties without specifying the language version are considered _invalid_.
Invalid specifications are deprecated and will become build errors in Gradle 8.0.

See more details about toolchain configuration in the <<toolchains#sec:configuring_toolchain_specifications,user manual>>.
    Registered: Wed Jun 12 18:38:38 UTC 2024
    - Last Modified: Mon Apr 01 15:00:23 UTC 2024
    - 87.7K bytes
    - Viewed (0)
Back to top