- Sort Score
- Result 10 results
- Languages All
Results 211 - 220 of 4,082 for THAT (0.02 sec)
-
docs/contribute/concurrency.md
### Locks We have 3 different things that we synchronize on. #### Http2Connection
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Sun Feb 06 16:35:36 UTC 2022 - 7K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/RequestBody.kt
* is transmitted. If you cannot ensure that your client and server both support HTTP/2, do not * use this feature. * * ### Duplex APIs * * With regular request bodies it is not legal to write bytes to the sink passed to * [RequestBody.writeTo] after that method returns. For duplex requests bodies that condition is
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed Jun 04 17:43:43 UTC 2025 - 9K bytes - Viewed (0) -
guava-gwt/test/com/google/common/collect/testing/Testing.gwt.xml
<exclude name="**/testing/**"/> </source> <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package; seeRegistered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Fri Jul 19 16:02:36 UTC 2024 - 1.7K bytes - Viewed (0) -
android/guava/src/com/google/common/util/concurrent/UncheckedExecutionException.java
* https://github.com/jspecify/jspecify-reference-checker/blob/61aafa4ae52594830cfc2d61c8b113009dbdb045/src/main/java/com/google/jspecify/nullness/NullSpecTransfer.java#L789 * and https://github.com/jspecify/jspecify/issues/490. * * (Perhaps it should also have required that its cause was a RuntimeException. However, that
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Thu Feb 13 17:34:21 UTC 2025 - 4.2K bytes - Viewed (0) -
guava/src/com/google/common/base/NullnessCasts.java
@GwtCompatible final class NullnessCasts { /** * Accepts a {@code @Nullable T} and returns a plain {@code T}, without performing any check that * that conversion is safe. * * <p>This method is intended to help with usages of type parameters that have {@linkplain * ParametricNullness parametric nullness}. If a type parameter instead ranges over only non-nullRegistered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Wed Aug 13 20:49:47 UTC 2025 - 3.3K bytes - Viewed (0) -
compat/maven-builder-support/src/main/java/org/apache/maven/building/DefaultProblem.java
* under the License. */ package org.apache.maven.building; /** * Describes a problem that was encountered during settings building. A problem can either be an exception that was * thrown or a simple string message. In addition, a problem carries a hint about its source, e.g. the settings file * that exhibits the problem. * * @deprecated since 4.0.0, use {@link org.apache.maven.api.services} instead */Registered: Sun Sep 07 03:35:12 UTC 2025 - Last Modified: Wed Jul 23 17:27:08 UTC 2025 - 4.4K bytes - Viewed (0) -
android/guava/src/com/google/common/net/InternetDomainName.java
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Thu Aug 07 16:05:33 UTC 2025 - 27.9K bytes - Viewed (0) -
android/guava/src/com/google/common/base/Preconditions.java
* nullness checker can already "prove" are non-null. That means that the first parameter to * checkNotNull *should* be annotated to require it to be non-null. * * However, for a variety of reasons, Google developers have written a ton of code over the past * decade that assumes that they can use checkNotNull for non-precondition checks. I had hoped to
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Thu Jul 10 22:11:00 UTC 2025 - 53K bytes - Viewed (0) -
android/guava/src/com/google/common/util/concurrent/ExecutionList.java
* that every {@code Runnable} that is {@linkplain #add added} will be executed after {@link * #execute()} is called. Any {@code Runnable} added after the call to {@code execute} is still * guaranteed to execute. There is no guarantee, however, that listeners will be executed in the * order that they are added. *Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Sun Dec 22 03:38:46 UTC 2024 - 6.9K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/Authenticator.kt
* * Implementations authenticate by returning a follow-up request that includes an authorization * header, or they may decline the challenge by returning null. In this case the unauthenticated * response will be returned to the caller that triggered it. * * Implementations should check if the initial request already included an attempt to * authenticate. If so it is likely that further attempts will not be useful and the authenticator
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Fri Dec 27 13:39:56 UTC 2024 - 5.5K bytes - Viewed (0)