- Sort Score
- Result 10 results
- Languages All
Results 341 - 350 of 1,006 for want (0.07 sec)
-
android/guava-testlib/test/com/google/common/testing/FakeTickerTest.java
import junit.framework.TestCase; import org.checkerframework.checker.nullness.qual.Nullable; /** * Unit test for {@link FakeTicker}. * * @author Jige Yu */ @GwtCompatible(emulated = true) // We also want to test the TimeUnit overload (especially under GWT, where it's the only option). @SuppressWarnings("SetAutoIncrementStep_Nanos") public class FakeTickerTest extends TestCase { @GwtIncompatible // NullPointerTester
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Tue Oct 22 13:49:09 UTC 2024 - 6.5K bytes - Viewed (0) -
android/guava-tests/test/com/google/common/reflect/SubtypeTester.java
* * <p>Tests should inherit from this class, and declare subtyping relationship with public methods * annotated by {@link TestSubtype}. * * <p>These declaration methods rely on Java static type checking to make sure what we want to * assert as subtypes are really subtypes according to javac. For example: * * <pre>{@code * class MySubtypeTests extends SubtypeTester { * @TestSubtype(suppressGetSubtype = true, suppressGetSupertype = true)
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Wed Apr 19 19:24:36 UTC 2023 - 6.1K bytes - Viewed (0) -
guava/src/com/google/common/base/StandardSystemProperty.java
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Thu Feb 23 15:09:35 UTC 2023 - 5K bytes - Viewed (0) -
README.md
<!-- References --> [using Guava in your build]: https://github.com/google/guava/wiki/UseGuavaInYourBuild [repackage]: https://github.com/google/guava/wiki/UseGuavaInYourBuild#what-if-i-want-to-use-beta-apis-from-a-library-that-people-use-as-a-dependency
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Tue Sep 24 18:34:38 UTC 2024 - 5.9K bytes - Viewed (0) -
android/guava-tests/test/com/google/common/collect/MultisetsCollectionTest.java
/* * When a test requests a multiset with duplicates, our plan of * "add an extra item 0 to A and an extra item 1 to B" really means * "add an extra item 0 to A and B," which isn't what we want. */ if (!Objects.equal(elements[0], elements[1])) { multiset2.add(elements[1], 2); } } return intersection(multiset1, multiset2); } };
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Wed Oct 30 16:15:19 UTC 2024 - 9.6K bytes - Viewed (0) -
guava/pom.xml
<!-- Even after we stop using JSR305 annotations in our own code, we'll want this link so that NullPointerTester's docs can link to @CheckForNull and friends... at least once we start using this config for guava-testlib. --> <offlineLink>
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Wed Jul 24 18:53:31 UTC 2024 - 9.1K bytes - Viewed (0) -
ci/official/utilities/setup.sh
# Load those stored pre-existing TFCI_ vars, if any if [[ -s "$FROM_ENV" ]]; then echo '==TFCI==: NOTE: Loading the following env parameters, which were' echo 'already set in the shell environment. If you want to disable this' echo 'behavior, create a new shell.' cat "$FROM_ENV" source "$FROM_ENV" rm "$FROM_ENV" fi fi # If building installer wheels, set the required environment variables that are
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Wed Aug 07 23:01:25 UTC 2024 - 6K bytes - Viewed (0) -
helm-releases/minio-4.0.12.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...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Aug 14 05:50:43 UTC 2022 - 19.4K bytes - Viewed (0) -
helm-releases/minio-4.0.13.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...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Tue Aug 23 18:18:14 UTC 2022 - 19.5K bytes - Viewed (0) -
helm-releases/minio-4.0.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...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Jul 16 06:42:56 UTC 2022 - 18.3K bytes - Viewed (0)