- Sort Score
- Result 10 results
- Languages All
Results 51 - 58 of 58 for exercise (0.15 sec)
-
okhttp/src/main/kotlin/okhttp3/Connection.kt
* HTTP request/response exchanges. Connections may be direct to the origin server or via a proxy. * * Typically instances of this class are created, connected and exercised automatically by the HTTP * client. Applications may use this class to monitor HTTP connections as members of a * [connection pool][ConnectionPool]. *
Registered: Sun Jun 16 04:42:17 UTC 2024 - Last Modified: Wed Dec 20 23:27:07 UTC 2023 - 4.3K bytes - Viewed (0) -
src/cmd/go/testdata/script/work_vendor_prune_all.txt
# This test exercises that vendoring works properly using the workspace in the # the work_prune test case. go work vendor cmp vendor/modules.txt modules.txt.want go list -f '{{with .Module}}{{.Path}}@{{.Version}}{{end}}' all cmp stdout want_versions go list -f '{{.Dir}}' example.com/q stdout $GOPATH[\\/]src[\\/]vendor[\\/]example.com[\\/]q go list -f '{{.Dir}}' example.com/b stdout $GOPATH[\\/]src[\\/]vendor[\\/]example.com[\\/]b
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Fri Aug 11 01:59:23 UTC 2023 - 3.4K bytes - Viewed (0) -
guava-tests/test/com/google/common/util/concurrent/AggregateFutureStateFallbackAtomicHelperTest.java
* the strategy is selected in the static initializer of AggregateFutureState. This is convenient * and performant but introduces some testing difficulties. This test exercises the two fallback * strategies. * * <ul> * <li>SafeAtomicHelper: uses Atomic FieldsUpdaters to implement synchronization * <li>SynchronizedHelper: uses {@code synchronized} blocks for synchronization * </ul>
Registered: Wed Jun 12 16:38:11 UTC 2024 - Last Modified: Mon Oct 10 19:45:10 UTC 2022 - 5.9K bytes - Viewed (0) -
android/guava-tests/test/com/google/common/util/concurrent/AbstractFutureFallbackAtomicHelperTest.java
* selected in the static initializer of AbstractFuture. This is convenient and performant but * introduces some testing difficulties. This test exercises the two fallback strategies in abstract * future. * * <ul> * <li>SafeAtomicHelper: uses AtomicReferenceFieldsUpdaters to implement synchronization
Registered: Wed Jun 12 16:38:11 UTC 2024 - Last Modified: Fri Jun 07 22:25:23 UTC 2024 - 6.3K bytes - Viewed (0) -
guava-tests/test/com/google/common/util/concurrent/AbstractFutureFallbackAtomicHelperTest.java
* selected in the static initializer of AbstractFuture. This is convenient and performant but * introduces some testing difficulties. This test exercises the two fallback strategies in abstract * future. * * <ul> * <li>SafeAtomicHelper: uses AtomicReferenceFieldsUpdaters to implement synchronization
Registered: Wed Jun 12 16:38:11 UTC 2024 - Last Modified: Fri Jun 07 22:25:23 UTC 2024 - 6.3K bytes - Viewed (0) -
platforms/core-runtime/launcher/src/integTest/groovy/org/gradle/launcher/continuous/SimpleJavaContinuousIntegrationTest.groovy
then: noBuildTriggered() when: sourceFile.text = "class Thing {}" then: buildTriggeredAndSucceeded() } // Just exercises the dependency management layers to shake out any weirdness @Requires(UnitTestPreconditions.Online) def "can resolve dependencies from remote repository"() { when:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Sep 22 09:29:13 UTC 2023 - 8.3K bytes - Viewed (0) -
src/os/path_windows_test.go
"os" "path/filepath" "strings" "syscall" "testing" ) func TestAddExtendedPrefix(t *testing.T) { // Test addExtendedPrefix instead of fixLongPath so the path manipulation code // is exercised even if long path are supported by the system, else the // function might not be tested at all if/when all test builders support long paths. cwd, err := os.Getwd() if err != nil { t.Fatal("cannot get cwd") }
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Apr 23 16:37:32 UTC 2024 - 8K bytes - Viewed (0) -
samples/ambient-argo/README.md
responsible for providing the AppDev with a comprehensive application platform, which simplifies getting the application from Source Control to Production, as well as operating the App in Production. As such, the PlatEng team must have a good deal of expertise in installing, operating, and automating a broad array of Cloud Native technologies, such as Service Mesh, Kubernetes, Observability stores and consumers, GitOps tooling, Policy enforcement, and templating tools such as Crossplane. Due to this breadth,...
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Sat Nov 04 01:54:50 UTC 2023 - 8.7K bytes - Viewed (0)