- Sort Score
- Result 10 results
- Languages All
Results 31 - 40 of 148 for Scans (0.03 sec)
-
gradle.properties
org.gradle.kotlin.dsl.allWarningsAsErrors=true # Kotlin settings kotlin.incremental.useClasspathSnapshot=true kotlin.stdlib.default.dependency=false kotlin.js.ir.output.granularity=whole-program # Temporarily force IDEs to produce build scans systemProp.org.gradle.internal.ide.scan=true # If you're experimenting with changes and don't want to update the verification file right away, please change the mode to "lenient" (not "off") org.gradle.dependency.verification=strict
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Jun 11 16:35:19 UTC 2024 - 1.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/01-core-dependency-management/core_dependency_management.adoc
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Nov 29 17:38:38 UTC 2023 - 4.6K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/licenses.adoc
[[licenses:build_scan_plugin]] == Gradle Build Scan Plugin
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 27 17:53:42 UTC 2023 - 1.3K bytes - Viewed (0) -
platforms/enterprise/enterprise/src/integTest/groovy/org/gradle/internal/enterprise/legacy/LegacyGradleEnterpriseCheckInConfigCachingIntegTest.groovy
} buildFile << """ task t """ when: succeeds "t", "--configuration-cache" then: scanPlugin.assertUnsupportedMessage(output, "Build scans have been disabled due to incompatibility between your Gradle Enterprise plugin version (3.3.4) and configuration caching. Please use Gradle Enterprise plugin version 3.4 or later for compatibility with configuration caching.") }
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Apr 24 13:28:46 UTC 2024 - 1.8K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/optimizing-performance/performance.adoc
Neither will a project with lots of inter-subproject dependencies. But most multi-subproject builds see a reduction in build times. === Visualize parallelism with build scans Build scans give you a visual timeline of task execution. In the following example build, you can see long-running tasks at the beginning and end of the build:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Feb 23 03:39:56 UTC 2024 - 33.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/troubleshooting.adoc
You can see a dependency tree and see which resolved dependency versions differed from what was requested by clicking the _Dependencies_ view and using the search functionality, specifying the resolution reason. .Debugging dependency conflicts with build scans image::troubleshooting-dependency-management-build-scan.png[]
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat Apr 06 02:22:03 UTC 2024 - 11.5K bytes - Viewed (0) -
src/image/names.go
func (c *Uniform) At(x, y int) color.Color { return c.C } func (c *Uniform) RGBA64At(x, y int) color.RGBA64 { r, g, b, a := c.C.RGBA() return color.RGBA64{uint16(r), uint16(g), uint16(b), uint16(a)} } // Opaque scans the entire image and reports whether it is fully opaque. func (c *Uniform) Opaque() bool { _, _, _, a := c.C.RGBA() return a == 0xffff } // NewUniform returns a new [Uniform] image of the given color.
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Thu Oct 19 12:02:45 UTC 2023 - 1.5K bytes - Viewed (0) -
tensorflow/compiler/mlir/tfr/passes/passes.h
#include "mlir/IR/BuiltinOps.h" // from @llvm-project #include "mlir/Pass/Pass.h" // from @llvm-project #include "mlir/Support/LogicalResult.h" // from @llvm-project namespace mlir { namespace TFR { // Scans the func op and adds all the canonicalization patterns of the ops // except the tf ops, inside the function. void populateCanonicalizationPatterns(func::FuncOp func, RewritePatternSet &patterns);
Registered: Sun Jun 16 05:45:23 UTC 2024 - Last Modified: Thu Jun 08 01:19:25 UTC 2023 - 2K bytes - Viewed (0) -
src/index/suffixarray/sais.go
// and always room at the top level), which eliminates all but // the first freq_I_B text scans (that is, 5 of the 6). // So the top level of the recursion only does 22 - 6 - 5 = 11 // input-sized scans and a typical level does 16 scans. // // The linear scans do not cost anywhere near as much as // the random accesses to the text made during a few of // the scans (specifically #6, #9, #16, #19, #22 marked above).
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Mon Mar 18 23:57:18 UTC 2024 - 32.4K bytes - Viewed (0) -
platforms/jvm/language-java/src/main/java/org/gradle/api/internal/tasks/compile/AnnotationProcessorDiscoveringCompiler.java
spec.setEffectiveAnnotationProcessors(annotationProcessors); return delegate.execute(spec); } /** * Scans the processor path for processor declarations. Filters them if the explicit <code>-processor</code> argument is given. * Treats explicit processors that didn't have a matching declaration on the path as non-incremental. */
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Dec 11 13:37:56 UTC 2023 - 3.8K bytes - Viewed (0)