- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 13 for hexarchy (0.31 sec)
-
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
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun May 05 22:45:11 GMT 2024 - 3.4K 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
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Mar 06 23:02:25 GMT 2024 - 4K 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`:
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Jan 11 21:21:35 GMT 2024 - 20.5K 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.
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) -
ChangeLog.md
- [`KT-57521`](https://youtrack.jetbrains.com/issue/KT-57521) MPP: Compiler options declared in places other than languageSettings don't reach shared source sets - [`KT-58676`](https://youtrack.jetbrains.com/issue/KT-58676) Enable default Kotlin Target Hierarchy by default
Plain Text - Registered: Fri May 03 08:18:13 GMT 2024 - Last Modified: Thu Dec 21 17:48:12 GMT 2023 - 268.7K bytes - Viewed (1) -
analysis/analysis-api-fir/src/org/jetbrains/kotlin/analysis/api/fir/diagnostics/KtFirDataClassConverters.kt
firSymbolBuilder.buildSymbol(firDiagnostic.a), firDiagnostic as KtPsiDiagnostic, token, ) } add(FirErrors.CYCLIC_INHERITANCE_HIERARCHY) { firDiagnostic -> CyclicInheritanceHierarchyImpl( firDiagnostic as KtPsiDiagnostic, token, ) } add(FirErrors.EXPANDED_TYPE_CANNOT_BE_INHERITED) { firDiagnostic ->
Plain Text - Registered: Fri Apr 26 08:18:10 GMT 2024 - Last Modified: Wed Apr 24 09:49:26 GMT 2024 - 208.3K bytes - Viewed (0) -
analysis/analysis-api-fir/src/org/jetbrains/kotlin/analysis/api/fir/references/KDocReferenceResolver.kt
/** * Finds the parent symbol of the given KtSymbol by traversing back up the symbol hierarchy a certain number of steps, * or until the containing class or object symbol is found. * * @param symbol The KtSymbol whose parent symbol needs to be found. * @param goBackSteps The number of steps to go back up the symbol hierarchy. * @param selectedFqName The fully qualified name of the selected package.
Plain Text - Registered: Fri Apr 26 08:18:10 GMT 2024 - Last Modified: Fri Apr 19 11:06:47 GMT 2024 - 22.6K bytes - Viewed (0) -
RELEASE.md
## Tensorflow ### Breaking Changes * Support for Python 3.8 has been removed starting with TF 2.14. The TensorFlow 2.13.1 patch release will still have Python 3.8 support. * `tf.Tensor`
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Mon Apr 29 19:17:57 GMT 2024 - 727.7K bytes - Viewed (8) -
operator/README.md
#### Output to dirs The output of the manifest is concatenated into a single file. To generate a directory hierarchy with subdirectory levels representing a child dependency, use the following command: ```bash istioctl manifest generate -o istio_manifests ``` Use depth first search to traverse the created directory hierarchy when applying your YAML files. This is needed for
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Sun Sep 17 08:27:52 GMT 2023 - 17.5K 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
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 3.4K bytes - Viewed (0)