- Sort Score
- Num 10 results
- Language All
Results 401 - 410 of 1,127 for want (0.04 seconds)
-
docs/en/docs/how-to/migrate-from-pydantic-v1-to-pydantic-v2.md
/// warning The Pydantic team stopped support for Pydantic v1 for the latest versions of Python, starting with **Python 3.14**. This includes `pydantic.v1`, which is no longer supported in Python 3.14 and above. If you want to use the latest features of Python, you will need to make sure you use Pydantic v2. ///
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 05 18:13:19 GMT 2026 - 5.4K bytes - Click Count (0) -
helm-releases/minio-4.0.10.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 Apr 05 19:28:12 GMT 2026 - Last Modified: Thu Aug 04 16:09:22 GMT 2022 - 19.2K bytes - Click Count (0) -
helm-releases/minio-4.0.14.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 Apr 05 19:28:12 GMT 2026 - Last Modified: Mon Sep 05 01:06:49 GMT 2022 - 19.6K bytes - Click Count (0) -
helm-releases/minio-4.0.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 Apr 05 19:28:12 GMT 2026 - Last Modified: Thu Jul 28 03:54:38 GMT 2022 - 18.6K bytes - Click Count (0) -
helm-releases/minio-3.6.2.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 Apr 05 19:28:12 GMT 2026 - Last Modified: Thu Mar 17 18:30:55 GMT 2022 - 17.9K bytes - Click Count (0) -
android/guava/src/com/google/common/base/Converter.java
* Converter.apply (like Converter.convert) is capable of accepting null inputs. However, a * supertype of `Function<A, B>` turns out to be massively more useful to callers in practice: They * want their output to be non-null in operations like `stream.map(myConverter)`, and we can * guarantee that as long as we also require the input type to be non-null[*] (which is a * requirement that existing callers already fulfill).
Created: Fri Apr 03 12:43:13 GMT 2026 - Last Modified: Wed Jun 18 21:43:06 GMT 2025 - 22.8K bytes - Click Count (0) -
compat/maven-compat/src/main/java/org/apache/maven/artifact/resolver/ArtifactResolutionResult.java
import org.apache.maven.artifact.repository.ArtifactRepository; import org.apache.maven.artifact.versioning.OverConstrainedVersionException; /** * Specific problems during resolution that we want to account for: * <ul> * <li>missing metadata</li> * <li>version range violations</li> * <li>version circular dependencies</li> * <li>missing artifacts</li> * <li>network/transfer errors</li>
Created: Sun Apr 05 03:35:12 GMT 2026 - Last Modified: Fri Jun 06 14:28:57 GMT 2025 - 10K bytes - Click Count (0) -
benchmarks/src/main/java/org/elasticsearch/benchmark/search/aggregations/bucket/terms/LongKeyedBucketOrdsBenchmark.java
private final BigArrays bigArrays = new BigArrays(recycler, null, "REQUEST"); /** * Force loading all of the implementations just for extra paranoia's sake. * We really don't want the JVM to be able to eliminate one of them just * because we don't use it in the particular benchmark. That is totally a * thing it'd do. It is sneaky. */ @Setup
Created: Wed Apr 08 16:19:15 GMT 2026 - Last Modified: Fri Feb 19 20:59:23 GMT 2021 - 8.4K bytes - Click Count (0) -
build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/test/ErrorReportingTestListener.java
} public Set<Descriptor> getFailedTests() { return failedTests; } /** * Class for identifying test output sources. We use this rather than Gradle's {@link TestDescriptor} as we want * to avoid any nasty memory leak issues that come from keeping Gradle implementation types in memory. Since we * use this a the key for our HashMap, it's best to control the implementation as there's no guarantee that Gradle'sCreated: Wed Apr 08 16:19:15 GMT 2026 - Last Modified: Tue Jun 01 09:19:30 GMT 2021 - 10.7K bytes - Click Count (0) -
compat/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/AbstractArtifactResolutionException.java
Created: Sun Apr 05 03:35:12 GMT 2026 - Last Modified: Tue Apr 01 21:22:14 GMT 2025 - 10.1K bytes - Click Count (0)