- Sort Score
- Num 10 results
- Language All
Results 391 - 400 of 567 for wantCS (0.04 seconds)
The search processing time has exceeded the limit. The displayed results may be partial.
-
okhttp/src/jvmTest/kotlin/okhttp3/internal/tls/ClientAuthTest.kt
} private fun buildServerSslSocketFactory(): SSLSocketFactory { // The test uses JDK default SSL Context instead of the Platform provided one // as Conscrypt seems to have some differences, we only want to test client side here. return try { val keyManager = newKeyManager( null, serverCert, serverIntermediateCa.certificate, ) val trustManager =
Created: Fri Dec 26 11:42:13 GMT 2025 - Last Modified: Tue Nov 04 19:13:52 GMT 2025 - 13K bytes - Click Count (0) -
android/guava/src/com/google/common/eventbus/SubscriberRegistry.java
* (thanks to the checkArgument calls in getAnnotatedMethodsNotCached). If it happens, we'd * prefer to propagate an IllegalArgumentException to the caller. However, we don't want to * simply rethrow an exception (e.getCause()) that may in rare cases have come from another * thread. To accomplish both goals, we wrap that IllegalArgumentException in a new * instance.
Created: Fri Dec 26 12:43:10 GMT 2025 - Last Modified: Tue Jul 08 18:32:10 GMT 2025 - 10.8K bytes - Click Count (0) -
build-logic/cleanup/src/main/java/gradlebuild/cleanup/services/KillLeakingJavaProcesses.java
* Because the step is not guaranteed to run (e.g. build timeout), we need `KILL_LEAKED_PROCESSES_FROM_PREVIOUS_BUILDS` mode. */ KILL_PROCESSES_STARTED_BY_GRADLE, /** * Run when we want to retry the build. Kill all Gradle processes, regardless of they're global or local. */ KILL_ALL_GRADLE_PROCESSES } private static final Pattern UNIX_PID_PATTERN = Pattern.compile("([0-9]+)");
Created: Wed Dec 31 11:36:14 GMT 2025 - Last Modified: Tue Sep 23 13:49:45 GMT 2025 - 12K bytes - Click Count (0) -
helm-releases/minio-3.5.4.tgz
version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Mon Feb 14 06:04:53 GMT 2022 - 17.2K bytes - Click Count (0) -
helm-releases/minio-3.5.5.tgz
version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Wed Feb 16 19:44:53 GMT 2022 - 17.2K bytes - Click Count (0) -
helm-releases/minio-3.5.7.tgz
version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Feb 20 08:55:08 GMT 2022 - 17.6K bytes - Click Count (0) -
helm-releases/minio-3.5.8.tgz
version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Feb 27 06:44:38 GMT 2022 - 17.7K bytes - Click Count (0) -
helm-releases/minio-3.6.1.tgz
version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Mar 15 00:13:17 GMT 2022 - 17.9K bytes - Click Count (0) -
helm-releases/minio-3.4.6.tgz
version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ----------...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sat Jan 08 06:24:06 GMT 2022 - 15.2K bytes - Click Count (0) -
helm-releases/minio-3.4.8.tgz
version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ----------...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Jan 28 18:33:38 GMT 2022 - 15.2K bytes - Click Count (0)