- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 21 for entirely (0.06 sec)
-
android/guava/src/com/google/common/primitives/UnsignedLongs.java
decodeException.initCause(e); throw decodeException; } } /* * We move the static constants into this class so ProGuard can inline UnsignedLongs entirely * unless the user is actually calling a parse method. */ private static final class ParseOverflowDetection { private ParseOverflowDetection() {} // calculated as 0xffffffffffffffff / radix
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Mon Aug 11 19:31:30 UTC 2025 - 17.8K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/RealCall.kt
if (!timeout.exit()) return cause val e = InterruptedIOException("timeout") if (cause != null) e.initCause(cause) return e } /** * Stops applying the timeout before the call is entirely complete. This is used for WebSockets * and duplex calls where the timeout only applies to the initial setup. */ fun timeoutEarlyExit() { check(!timeoutEarlyExit) timeoutEarlyExit = true
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Sat Aug 30 11:30:11 UTC 2025 - 17.8K bytes - Viewed (0) -
android/guava/src/com/google/common/reflect/TypeResolver.java
* * 2a. If the resolved types are identical to the original types, then we can return the * original, identical JDK TypeVariable. By doing so, we sidestep the problem entirely. * * 2b. If the resolved types are different from the original types, things are trickier. The * only way to get a TypeVariable instance for the resolved types is to create our own. The
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Wed Sep 03 14:03:14 UTC 2025 - 24.2K bytes - Viewed (0) -
guava/src/com/google/common/reflect/TypeResolver.java
* * 2a. If the resolved types are identical to the original types, then we can return the * original, identical JDK TypeVariable. By doing so, we sidestep the problem entirely. * * 2b. If the resolved types are different from the original types, things are trickier. The * only way to get a TypeVariable instance for the resolved types is to create our own. The
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Wed Sep 03 14:03:14 UTC 2025 - 24.2K bytes - Viewed (0) -
android/guava/src/com/google/common/collect/TreeRangeSet.java
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Mon Aug 11 19:31:30 UTC 2025 - 32.3K bytes - Viewed (0) -
guava/src/com/google/common/collect/ImmutableSet.java
* type conveys the immutability guarantee. */ public static <E> ImmutableSet<E> of(E e1) { return new SingletonImmutableSet<>(e1); } /* * TODO: b/315526394 - Skip the Builder entirely for the of(...) methods, since we don't need to * worry that we might trigger the fallback to the JDK-backed implementation? (The varargs one
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Thu Aug 07 16:05:33 UTC 2025 - 35.2K bytes - Viewed (0) -
android/guava/src/com/google/common/util/concurrent/Futures.java
* type. So why even make that error possible by giving callers the choice? * * On the other hand, the current signature is consistent with the similar allAsList method. And * eventually this method may go away entirely in favor of an API like * whenAllComplete().collectSuccesses(). That API would have a signature more like the current * one. */ return new ListFuture<V>(ImmutableList.copyOf(futures), false); }
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Thu Aug 07 16:05:33 UTC 2025 - 64.3K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.31.md
- Fix a scheduler preemption issue where the victim pod was not deleted due to incorrect status patching. This issue occurred when the preemptor and victim pods had different QoS classes in their status, causing the preemption to fail entirely. ([#126691](https://github.com/kubernetes/kubernetes/pull/126691), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling]
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Wed Aug 13 19:49:57 UTC 2025 - 429.6K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.32.md
- Fixed a scheduler preemption issue where the victim pod was not deleted due to incorrect status patching. This issue occurred when the preemptor and victim pods had different QoS classes in their status, causing the preemption to fail entirely. ([#126644](https://github.com/kubernetes/kubernetes/pull/126644), [@Huang-Wei](https://github.com/Huang-Wei))
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Wed Aug 13 14:49:49 UTC 2025 - 412.3K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.34.md
- Skipped pod backoff entirely when the `PodMaxBackoffDuration` kube-scheduler option was set to zero and the `SchedulerPopFromBackoffQ` feature gate was enabled. ([#131965](https://github.com/kubernetes/kubernetes/pull/131965), [@macsko](https://github.com/macsko))
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Wed Aug 27 10:36:10 UTC 2025 - 292.8K bytes - Viewed (0)