- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 417 for Pairing (0.21 sec)
-
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) -
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) -
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) -
docs/de/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: Sat Mar 30 18:19:25 GMT 2024 - 10.1K bytes - Viewed (0) -
cni/pkg/repair/repair_test_helpers.go
State: corev1.ContainerState{ Waiting: &corev1.ContainerStateWaiting{ Reason: "PodInitializing", }, }, }, }, }, } return pod } // Container specs var ( brokenInitContainerWaiting = corev1.ContainerStatus{ Name: constants.ValidationContainerName, State: corev1.ContainerState{ Waiting: &corev1.ContainerStateWaiting{ Reason: "CrashLoopBackOff",
Go - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri May 12 17:39:53 GMT 2023 - 4.7K bytes - Viewed (0) -
ci/official/bisect.sh
# Run any CI script and env configuration to bisect a failing target in some # build configuration. You must set the following variables to control this # script: # # TF_BISECT_GOOD: Last known good commit (e.g. commit from the last passing job) # TF_BISECT_BAD: First bad commit (e.g. commit from the first failing job) # TF_BISECT_SCRIPT: The build script path relative to the TF root dir, e.g.
Shell Script - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Feb 01 03:21:19 GMT 2024 - 1.8K bytes - Viewed (0) -
docs/zh/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 - 8.7K 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) -
docs/ja/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 - 11.2K bytes - Viewed (0)