- Sort Score
- Result 10 results
- Languages All
Results 501 - 510 of 783 for field33 (0.05 sec)
-
android/guava-testlib/src/com/google/common/collect/testing/testers/AbstractListTester.java
@SuppressWarnings("JUnit4ClassUsedInJUnit3") public class AbstractListTester<E extends @Nullable Object> extends AbstractCollectionTester<E> { /* * Previously we had a field named list that was initialized to the value of * collection in setUp(), but that caused problems when a tester changed the * value of list or collection but not both. */ protected final List<E> getList() {
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Wed Oct 30 16:15:19 UTC 2024 - 2.8K bytes - Viewed (0) -
guava/src/com/google/common/io/ByteArrayDataInput.java
@CanIgnoreReturnValue // to skip some bytes @Override double readDouble(); @CanIgnoreReturnValue // to skip a line @Override @CheckForNull String readLine(); @CanIgnoreReturnValue // to skip a field @Override String readUTF();
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Tue Feb 28 20:13:02 UTC 2023 - 2.8K bytes - Viewed (0) -
helm-releases/minio-4.0.11.tgz
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 Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set k...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Aug 07 05:41:47 UTC 2022 - 19.2K bytes - Viewed (0) -
helm-releases/minio-4.0.2.tgz
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 Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set k...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon May 09 04:25:47 UTC 2022 - 18K bytes - Viewed (0) -
helm-releases/minio-4.0.3.tgz
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 Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set k...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Jul 08 06:16:22 UTC 2022 - 18K bytes - Viewed (0) -
helm-releases/minio-5.0.6.tgz
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 Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set k...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon Feb 13 06:53:06 UTC 2023 - 20.3K bytes - Viewed (0) -
helm-releases/minio-5.0.0.tgz
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 Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set k...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Tue Oct 25 10:20:22 UTC 2022 - 19.8K bytes - Viewed (0) -
compat/maven-plugin-api/src/main/java/org/apache/maven/plugin/lifecycle/Lifecycle.java
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 2.7K bytes - Viewed (0) -
internal/grid/trace.go
) // TraceParamsKey allows to pass trace parameters to the request via context. // This is only needed when un-typed requests are used. // MSS, map[string]string types are preferred, but any struct with exported fields will work. type TraceParamsKey struct{} // traceRequests adds request tracing to the connection. func (c *Connection) traceRequests(p *pubsub.PubSub[madmin.TraceInfo, madmin.TraceType]) { c.trace = &tracer{
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Jun 01 05:17:37 UTC 2024 - 4.1K bytes - Viewed (0) -
cmd/erasure-metadata.go
} // ShardSize - returns actual shared size from erasure blockSize. func (e ErasureInfo) ShardSize() int64 { return ceilFrac(e.BlockSize, int64(e.DataBlocks)) } // IsValid - tells if erasure info fields are valid. func (fi FileInfo) IsValid() bool { if fi.Deleted { // Delete marker has no data, no need to check // for erasure coding information return true } dataBlocks := fi.Erasure.DataBlocks
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Oct 31 22:10:24 UTC 2024 - 21.3K bytes - Viewed (0)