- Sort Score
- Result 10 results
- Languages All
Results 21 - 30 of 643 for Reed (0.18 sec)
-
cmd/service.go
// freezeServices will freeze all incoming S3 API calls. // For each call, unfreezeServices must be called once. func freezeServices() { // Use atomics for globalServiceFreeze, so we can read without locking. // We need a lock since we are need the 2 atomic values to remain in sync. globalServiceFreezeMu.Lock() // If multiple calls, first one creates channel. globalServiceFreezeCnt++ if globalServiceFreezeCnt == 1 {
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Feb 28 07:02:14 GMT 2024 - 3.8K bytes - Viewed (0) -
architecture/standards/0003-avoid-introducing-Groovy-types-to-public-api.md
Doing this provides the following specific benefits: - **Reduce the API surface** - We no longer need to maintain two methods. - **Consistency** - All languages have consistent access to the same APIs and ergonomics in the DSL. - **Reduce the size of the Gradle distribution** - We no longer need to carry multiple standard libraries for different languages. ## Decision
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Sun Mar 10 20:38:06 GMT 2024 - 1.8K bytes - Viewed (0) -
configure.py
environ_cp['TF_NEED_CUDA'] = '0' else: environ_cp['TF_NEED_CUDA'] = str( int(get_var(environ_cp, 'TF_NEED_CUDA', 'CUDA', False))) if (environ_cp.get('TF_NEED_CUDA') == '1' and 'TF_CUDA_CONFIG_REPO' not in environ_cp): set_action_env_var( environ_cp, 'TF_NEED_TENSORRT', 'TensorRT', False, bazel_config_name='tensorrt')
Python - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Mon Apr 15 18:25:36 GMT 2024 - 53.8K bytes - Viewed (0) -
docs/en/docs/features.md
### Short It has sensible **defaults** for everything, with optional configurations everywhere. All the parameters can be fine-tuned to do what you need and to define the API you need. But by default, it all **"just works"**. ### Validation * Validation for most (or all?) Python **data types**, including: * JSON objects (`dict`).
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 9.3K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/lifecycle/MavenExecutionPlan.java
import org.apache.maven.plugin.descriptor.MojoDescriptor; // TODO lifecycles being executed // TODO what runs in each phase // TODO plugins that need downloading // TODO project dependencies that need downloading // TODO unfortunately the plugins need to be downloaded in order to get the plugin.xml file. need to externalize this // from the plugin archive. // TODO this will be the class that people get in IDEs to modify /**
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Jan 10 12:55:54 GMT 2024 - 6.2K bytes - Viewed (0) -
api/maven-api-core/src/main/java/org/apache/maven/api/services/LocalRepositoryManager.java
/** * * @since 4.0.0 */ @Experimental public interface LocalRepositoryManager extends Service { /** * Gets the relative path for a locally installed artifact. * Note that the artifact need not actually exist yet at * the returned location, the path merely indicates where * the artifact would eventually be stored. * * @param session The session to use, must not be {@code null}.
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Dec 08 09:10:49 GMT 2023 - 2.7K bytes - Viewed (0) -
docs/en/docs/tutorial/testing.md
Use the `TestClient` object the same way as you do with `httpx`. Write simple `assert` statements with the standard Python expressions that you need to check (again, standard `pytest`). ```Python hl_lines="2 12 15-18" {!../../../docs_src/app_testing/tutorial001.py!} ``` !!! tip Notice that the testing functions are normal `def`, not `async def`.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 6.2K bytes - Viewed (0) -
architecture-standards/0002-avoid-using-java-serialization.md
# ADR-0002 - Avoid using Java serialization ## Date 2012-12-01 ## Context In Gradle, we often need to serialize in-memory objects for caching or transmitting them across process barriers, etc. Java serialization is one way to implement this, however, despite its simplicity of implementation, it has several drawbacks:
Plain Text - Registered: Wed Feb 14 11:36:15 GMT 2024 - Last Modified: Thu Feb 08 21:48:27 GMT 2024 - 1.9K bytes - Viewed (0) -
android/guava/src/com/google/common/util/concurrent/AggregateFuture.java
handleAllCompleted(); return; } // NOTE: If we ever want to use a custom executor here, have a look at CombinedFuture as we'll // need to handle RejectedExecutionException if (allMustSucceed) { // We need fail fast, so we have to keep track of which future failed so we can propagate // the exception immediately
Java - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Feb 01 21:46:34 GMT 2024 - 15.4K bytes - Viewed (0) -
cni/pkg/nodeagent/informers.go
// We have no good way to distinguish between these two cases from here. But we don't need to! // Existing pods will be handled by the dataplane using `GetAmbientPods`, // and the initial enqueueNamespace, and new pods will be handled by the CNI. case controllers.EventUpdate: // For update, we just need to handle opt outs newPod := event.New.(*corev1.Pod) oldPod := event.Old.(*corev1.Pod)
Go - Registered: Wed May 01 22:53:12 GMT 2024 - Last Modified: Thu Feb 08 01:03:24 GMT 2024 - 9.9K bytes - Viewed (0)