- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for hold (2.49 sec)
-
okhttp-testing-support/src/main/kotlin/okhttp3/internal/concurrent/TaskFaker.kt
throw AssertionError("Thread ${Thread.currentThread().name} MUST hold lock on $this") } } @Suppress("NOTHING_TO_INLINE") internal inline fun Any.assertThreadDoesntHoldLock() { if (assertionsEnabled && taskRunner.lock.isHeldByCurrentThread) { throw AssertionError("Thread ${Thread.currentThread().name} MUST NOT hold lock on $this") } }
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Apr 29 00:33:04 GMT 2024 - 12.6K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/internal/concurrent/TaskRunner.kt
* * Use [INSTANCE] for a task runner that uses daemon threads. There is not currently a shared * instance for non-daemon threads. * * The task runner is also responsible for releasing held threads when the library is unloaded. * This is for the benefit of container environments that implement code unloading. * * Most applications should share a process-wide [TaskRunner] and use queues for per-client work. */
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Apr 29 00:33:04 GMT 2024 - 10.6K bytes - Viewed (0) -
okhttp/src/test/java/okhttp3/internal/concurrent/TaskRunnerTest.kt
"FINE: Q10000 finished run in 0 µs: task two", "FINE: Q10000 starting : task one", "FINE: Q10000 finished run in 0 µs: task one", ) } /** * The runner doesn't hold references to its queues! Otherwise we'd need a mechanism to clean them * up when they're no longer needed and that's annoying. Instead the task runner only tracks which * queues have work scheduled. */
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Apr 29 00:33:04 GMT 2024 - 23K bytes - Viewed (0)