- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 593 for Need (0.08 sec)
-
architecture/standards/0006-use-of-provider-apis-in-gradle.md
## Consequences * We are incurring debt that will need to be paid later via deprecations or breaking changes to existing classes. The implementation for some Gradle types will be more complicated than an equivalent clean-sheet implementation. * During code reviews that introduce new APIs, reviewers need to be mindful that all new properties are implemented with lazy types.
Registered: Wed Nov 06 11:36:14 UTC 2024 - Last Modified: Tue Oct 15 20:00:57 UTC 2024 - 10K bytes - Viewed (0) -
internal/bucket/bandwidth/reader.go
} else { // part of header can be accommodated r.opts.HeaderSize -= b - 1 need = 1 // to ensure we read at least one byte for every Read tokens = b } } else { // all tokens go towards payload need = int(math.Min(float64(b), float64(need))) tokens = need } // reduce tokens requested according to availability av := int(r.throttle.Tokens()) if av < tokens && av > 0 { tokens = av
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Jul 12 14:57:31 UTC 2024 - 3.2K bytes - Viewed (0) -
docs/en/docs/advanced/using-request-directly.md
Up to now, you have been declaring the parts of the request that you need with their types. Taking data from: * The path as parameters. * Headers. * Cookies. * etc. And by doing so, **FastAPI** is validating that data, converting it and generating documentation for your API automatically. But there are situations where you might need to access the `Request` object directly. ## Details about the `Request` object
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 2.3K bytes - Viewed (0) -
impl/maven-core/plugin-manager.txt
h2. Concerns for the plugin manager h3. Resolving the dependencies of a plugin
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 12.9K bytes - Viewed (0) -
docs/en/docs/tutorial/path-params-numeric-validations.md
/// ## Order the parameters as you need /// tip This is probably not as important or necessary if you use `Annotated`. /// Let's say that you want to declare the query parameter `q` as a required `str`. And you don't need to declare anything else for that parameter, so you don't really need to use `Query`.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 8.8K bytes - Viewed (0) -
impl/maven-core/lifecycle-executor.txt
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 9.7K bytes - Viewed (0) -
Makefile
# to build the repo. The only dependencies in this mode are to have make and # docker. If you'd rather build with a local tool chain instead, you'll need to # figure out all the tools you need in your environment to make that work. export BUILD_WITH_CONTAINER ?= 0 ifeq ($(BUILD_WITH_CONTAINER),1) # An export free of arguments in a Makefile places all variables in the Makefile into the
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Tue Jul 23 15:00:31 UTC 2024 - 2.3K bytes - Viewed (0) -
docs/en/docs/tutorial/background-tasks.md
## Caveat If you need to perform heavy background computation and you don't necessarily need it to be run by the same process (for example, you don't need to share memory, variables, etc), you might benefit from using other bigger tools like <a href="https://docs.celeryq.dev" class="external-link" target="_blank">Celery</a>.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 27 15:22:48 UTC 2024 - 4.8K bytes - Viewed (0) -
android/guava/src/com/google/common/hash/Hashing.java
hashFunctions[0] = Murmur3_128HashFunction.GOOD_FAST_HASH_128; int seed = GOOD_FAST_HASH_SEED; for (int i = 1; i < hashFunctionsNeeded; i++) { seed += 1500450271; // a prime; shouldn't matter hashFunctions[i] = murmur3_128(seed); } return new ConcatenatedHashFunction(hashFunctions); } /**
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Fri Jul 19 16:02:36 UTC 2024 - 29.3K 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)
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Oct 09 16:05:45 UTC 2024 - 11.7K bytes - Viewed (0)