- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for Scenario (0.06 sec)
-
okhttp/src/jvmTest/kotlin/okhttp3/CacheTest.kt
server.enqueue(builder.build()) if (responseCode == HttpURLConnection.HTTP_CLIENT_TIMEOUT) { // 408's are a bit of an outlier because we may repeat the request if we encounter this // response code. In this scenario, there are 2 responses: the initial 408 and then the 200 // because of the retry. We just want to ensure the initial 408 isn't cached. expectedResponseCode = 200 server.enqueue( MockResponse
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Sat Aug 16 09:39:51 UTC 2025 - 113.6K bytes - Viewed (0) -
cmd/object-handlers_test.go
} if testCase.copySourceRange != "" { if testCase.copySourceRange == "empty" { req.Header.Set("X-Amz-Copy-Source-Range", "") // specifically test for S3 errors in this scenario. } else { req.Header.Set("X-Amz-Copy-Source-Range", testCase.copySourceRange) } } // Since `apiRouter` satisfies `http.Handler` it has a ServeHTTP to execute the logic of the handler.Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 29 02:39:48 UTC 2025 - 163.1K bytes - Viewed (0) -
src/main/webapp/js/admin/popper.min.js.map
offset,\n /** @prop {Number|String} offset=0\n * The offset value as described in the modifier description\n */\n offset: 0,\n },\n\n /**\n * Modifier used to prevent the popper from being positioned outside the boundary.\n *\n * A scenario exists where the reference itself is not within the boundaries.<br />\n * We can say it has \"escaped the boundaries\" — or just \"escaped\".<br />\n * In this case we need to decide whether the popper should either:\n *\n * - detach from...Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Sat Oct 26 01:49:09 UTC 2024 - 120.9K bytes - Viewed (0) -
src/main/java/jcifs/smb/SmbFile.java
th.close(); } else { // Let connection pooling handle cleanup - this improves performance // for scenarios where the same file or directory is accessed multiple times log.trace("Tree handle released to connection pool for reuse"); // The connection pool will handle cleanup based on its own timeout settings
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 30 05:58:03 UTC 2025 - 103.2K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.5.md
deletion of the Node object, deletion of the instance in the cloud provider, or force deletion of the pod from the api-server). This helps prevent "split brain" scenarios in clustered applications by ensuring that unreachable pods will not be presumed dead unless some "fencing" operation has provided one of the above indications.Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Thu Dec 24 02:28:26 UTC 2020 - 136.4K bytes - Viewed (0)