- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 21 for hierarchy (0.11 sec)
-
android/guava/src/com/google/common/eventbus/SubscriberRegistry.java
identifiers.put(ident, method); } } } } return ImmutableList.copyOf(identifiers.values()); } /** Global cache of classes to their flattened hierarchy of supertypes. */ private static final LoadingCache<Class<?>, ImmutableSet<Class<?>>> flattenHierarchyCache = CacheBuilder.newBuilder() .weakKeys() .build( CacheLoader.from(
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Thu Oct 17 15:16:45 UTC 2024 - 10.8K bytes - Viewed (0) -
.teamcity/README.md
## Project structure Mostly a standard Maven project structure. The entry point `settings.kts` defines the TeamCity project. There are 3 subprojects in the TeamCity project hierarchy: `Check` for Gradle builds, `Promotion` for releasing Gradle versions, `Util` for miscellaneous utilities. ## Develop and verify
Registered: Wed Nov 06 11:36:14 UTC 2024 - Last Modified: Wed Mar 06 23:02:25 UTC 2024 - 4K bytes - Viewed (0) -
architecture/build-state-model.md
# Build state model The Gradle daemon tracks state for various elements. These are arranged in a hierarchy: ```mermaid graph TD process["build process"] session["build session"] process --> session build_tree["build tree"] session --> build_tree build1["root build"] build_tree --> build1 project1["root project"] build1 --> project1 project2["project"] build1 --> project2
Registered: Wed Nov 06 11:36:14 UTC 2024 - Last Modified: Wed May 22 13:39:49 UTC 2024 - 3.4K bytes - Viewed (0) -
docs/en/docs/benchmarks.md
The simpler the problem solved by the tool, the better performance it will get. And most of the benchmarks don't test the additional features provided by the tool. The hierarchy is like: * **Uvicorn**: an ASGI server * **Starlette**: (uses Uvicorn) a web microframework
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Thu Apr 18 19:53:19 UTC 2024 - 3.4K bytes - Viewed (0) -
cni/pkg/nodeagent/podcgroupns.go
} return r }, uid)) } // Cgroup represents a linux cgroup. type Cgroup struct { HierarchyID string ControllerList string GroupPath string } // GetCGroups returns a slice of cgroups for pid using fs for filesystem calls. // // The expected cgroup format is "hierarchy-ID:controller-list:cgroup-path", and // this function will return an error if every cgroup does not meet that format. //
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Apr 12 21:47:31 UTC 2024 - 11K bytes - Viewed (0) -
cmd/format-erasure.go
} `json:"xl"` } // formatErasureV3 struct is same as formatErasureV2 struct except that formatErasureV3.Erasure.Version is "3" indicating // the simplified multipart backend which is a flat hierarchy now. // In .minio.sys/multipart we have: // sha256(bucket/object)/uploadID/[xl.meta, part.1, part.2 ....] type formatErasureV3 struct { formatMetaV1 Erasure struct {
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri May 24 23:05:23 UTC 2024 - 23.2K bytes - Viewed (0) -
docs/en/docs/features.md
* Even dependencies can have dependencies, creating a hierarchy or **"graph" of dependencies**. * All **automatically handled** by the framework. * All the dependencies can require data from requests and **augment the path operation** constraints and automatic documentation.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Thu Aug 15 23:30:12 UTC 2024 - 9.2K bytes - Viewed (0) -
docs/en/docs/advanced/security/oauth2-scopes.md
The *path operation* itself also declares a scope, `"items"`, so this will also be in the list of `security_scopes.scopes` passed to `get_current_user`. Here's how the hierarchy of dependencies and scopes looks like: * The *path operation* `read_own_items` has: * Required scopes `["items"]` with the dependency: * `get_current_active_user`:
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Oct 29 11:02:16 UTC 2024 - 13.1K bytes - Viewed (0) -
guava/src/com/google/common/base/Throwables.java
} return throwable; } /** * Gets a {@code Throwable} cause chain as a list. The first entry in the list will be {@code * throwable} followed by its cause hierarchy. Note that this is a snapshot of the cause chain and * will not reflect any subsequent changes to the cause chain. * * <p>Here's an example of how it can be used to find specific types of exceptions in the cause
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Fri Jul 19 16:02:36 UTC 2024 - 20.7K bytes - Viewed (0) -
src/main/java/jcifs/smb/SmbFile.java
Registered: Sun Nov 03 00:10:13 UTC 2024 - Last Modified: Thu May 23 01:50:13 UTC 2024 - 82.3K bytes - Viewed (0)