- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 273 for WAITING (0.17 sec)
-
android/guava-tests/test/com/google/common/util/concurrent/GeneratedMonitorTest.java
SATISFIED_AND_OCCUPIED_BEFORE_ENTERING, SATISFIED_UNOCCUPIED_AND_INTERRUPTED_BEFORE_ENTERING, SATISFIED_BEFORE_WAITING, SATISFIED_WHILE_WAITING, SATISFIED_AND_INTERRUPTED_BEFORE_WAITING, UNSATISFIED_BEFORE_AND_WHILE_WAITING, UNSATISFIED_AND_INTERRUPTED_BEFORE_WAITING; @Override public String toString() { return CaseFormat.UPPER_UNDERSCORE.to(CaseFormat.UPPER_CAMEL, name()); }
Java - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Mon Apr 17 14:48:57 GMT 2023 - 26.1K bytes - Viewed (0) -
guava-tests/test/com/google/common/util/concurrent/GeneratedMonitorTest.java
SATISFIED_AND_OCCUPIED_BEFORE_ENTERING, SATISFIED_UNOCCUPIED_AND_INTERRUPTED_BEFORE_ENTERING, SATISFIED_BEFORE_WAITING, SATISFIED_WHILE_WAITING, SATISFIED_AND_INTERRUPTED_BEFORE_WAITING, UNSATISFIED_BEFORE_AND_WHILE_WAITING, UNSATISFIED_AND_INTERRUPTED_BEFORE_WAITING; @Override public String toString() { return CaseFormat.UPPER_UNDERSCORE.to(CaseFormat.UPPER_CAMEL, name()); }
Java - Registered: Fri Apr 12 12:43:09 GMT 2024 - Last Modified: Mon Apr 17 14:48:57 GMT 2023 - 27.4K bytes - Viewed (0) -
guava-testlib/src/com/google/common/testing/GcFinalization.java
* ordinary tests. * * <p>Failure of the expected event to occur within an implementation-defined "reasonable" time * period or an interrupt while waiting for the expected event will result in a {@link * RuntimeException}. * * <p>Here's an example that tests a {@code finalize} method: * * <pre>{@code * final CountDownLatch latch = new CountDownLatch(1);
Java - Registered: Fri Apr 19 12:43:09 GMT 2024 - Last Modified: Thu Feb 22 17:40:56 GMT 2024 - 11.6K bytes - Viewed (0) -
docs/en/docs/async.md
In this scenario of "fast food burgers with your crush", as there is a lot of waiting π, it makes a lot more sense to have a concurrent system βΈπβ―. This is the case for most of the web applications. Many, many users, but your server is waiting π for their not-so-good connection to send their requests. And then waiting π again for the responses to come back.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 23K bytes - Viewed (0) -
docs/en/docs/deployment/server-workers.md
[19511] [INFO] Started server process [19511] [19511] [INFO] Waiting for application startup. [19511] [INFO] Application startup complete. [19513] [INFO] Started server process [19513] [19513] [INFO] Waiting for application startup. [19513] [INFO] Application startup complete. [19514] [INFO] Started server process [19514] [19514] [INFO] Waiting for application startup. [19514] [INFO] Application startup complete.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 9.1K bytes - Viewed (0) -
internal/lsync/lrwmutex_test.go
panic("Failed to acquire read lock") } // fmt.Println("1st read lock acquired, waiting...") if !lrwm.GetRLock(ctx, "", "object1", time.Second) { panic("Failed to acquire read lock") } // fmt.Println("2nd read lock acquired, waiting...") go func() { time.Sleep(2 * time.Second) lrwm.RUnlock() // fmt.Println("1st read lock released, waiting...") }() go func() { time.Sleep(3 * time.Second) lrwm.RUnlock()
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sun Mar 05 04:57:35 GMT 2023 - 7.9K bytes - Viewed (0) -
android/guava-tests/test/com/google/common/util/concurrent/InterruptibleTaskTest.java
import junit.framework.TestCase; import org.checkerframework.checker.nullness.qual.Nullable; public final class InterruptibleTaskTest extends TestCase { // Regression test for a deadlock where a task could be stuck busy waiting for the task to // transition to DONE public void testInterruptThrows() throws Exception { final CountDownLatch isInterruptibleRegistered = new CountDownLatch(1); InterruptibleTask<@Nullable Void> task =
Java - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Wed Sep 06 17:04:31 GMT 2023 - 6.6K bytes - Viewed (0) -
docs/ko/docs/deployment/server-workers.md
[19511] [INFO] Started server process [19511] [19511] [INFO] Waiting for application startup. [19511] [INFO] Application startup complete. [19513] [INFO] Started server process [19513] [19513] [INFO] Waiting for application startup. [19513] [INFO] Application startup complete. [19514] [INFO] Started server process [19514] [19514] [INFO] Waiting for application startup. [19514] [INFO] Application startup complete.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 10.2K bytes - Viewed (0) -
internal/dsync/drwmutex_test.go
// fmt.Println("1st read lock released, waiting...") }() go func() { time.Sleep(3 * testDrwMutexAcquireTimeout) drwm2.RUnlock(context.Background()) // fmt.Println("2nd read lock released, waiting...") }() drwm3 := NewDRWMutex(ds, "simplelock") // fmt.Println("Trying to acquire write lock, waiting...") ctx3, cancel3 := context.WithCancel(context.Background())
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Dec 24 03:49:07 GMT 2022 - 9.7K bytes - Viewed (0) -
android/guava-testlib/src/com/google/common/testing/GcFinalization.java
* ordinary tests. * * <p>Failure of the expected event to occur within an implementation-defined "reasonable" time * period or an interrupt while waiting for the expected event will result in a {@link * RuntimeException}. * * <p>Here's an example that tests a {@code finalize} method: * * <pre>{@code * final CountDownLatch latch = new CountDownLatch(1);
Java - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Thu Feb 22 17:40:56 GMT 2024 - 11.6K bytes - Viewed (0)