- Sort Score
- Num 10 results
- Language All
Results 1 - 10 of 19 for completion (0.04 seconds)
-
cmd/batch-expire_test.go
# retainVersions: 5 # keep the latest 5 versions of the object including delete markers. notify: endpoint: https://notify.endpoint # notification endpoint to receive job completion status token: Bearer xxxxx # optional authentication token for the notification endpoint retry: attempts: 10 # number of retries for the job before giving upCreated: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Thu Aug 01 12:53:30 GMT 2024 - 5.5K bytes - Click Count (0) -
internal/event/config.go
func (q Queue) ToRulesMap() RulesMap { pattern := q.Filter.RuleList.Pattern() return NewRulesMap(q.Events, pattern, q.ARN.TargetID) } // Unused. Available for completion. type lambda struct { ARN string `xml:"CloudFunction"` } // Unused. Available for completion. type topic struct { ARN string `xml:"Topic" json:"Topic"` } // Config - notification configuration described in
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Aug 29 02:39:48 GMT 2025 - 8.4K bytes - Click Count (0) -
doc/README.md
## For the release team The `relnote` tool, at `golang.org/x/build/cmd/relnote`, operates on the files in `doc/next`. As a release cycle nears completion, run `relnote todo` to get a list of unfinished release note work. To prepare the release notes for a release, run `relnote generate`. That will merge the `.md` files in `next` into a single file.
Created: Tue Dec 30 11:13:12 GMT 2025 - Last Modified: Mon Jul 22 17:55:04 GMT 2024 - 3.1K bytes - Click Count (0) -
docs/batch-jobs/README.md
MinIO batch jobs framework also provides - Retrying a failed job automatically driven by user input - Monitoring job progress in real-time - Send notifications upon completion or failure to user configured target Following YAML describes the structure of a replication job, each value is documented and self-describing. ```yaml replicate: apiVersion: v1
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Thu Oct 06 06:00:43 GMT 2022 - 4.8K bytes - Click Count (0) -
build-logic/jvm/src/main/kotlin/gradlebuild/jvm/JvmCompilation.kt
import org.jetbrains.kotlin.gradle.tasks.KotlinCompile /** * Encapsulates the configuration for the compilation of a source set, including: * - The target JVM version * - Workarounds which may affect the way the compilation is performed * * The compilation workarounds include: * - Using JDK internal classes * - Using Java standard library APIs that were introduced after the JVM version they are targeting
Created: Wed Dec 31 11:36:14 GMT 2025 - Last Modified: Fri Sep 19 05:45:14 GMT 2025 - 5.8K bytes - Click Count (0) -
architecture/standards/0008-use-nullaway.md
and there are no missing null checks. ## Decision Use "NullAway" in JSpecify mode to check for null-related errors in Java code. Consider improper uses of `null` detected by NullAway a compilation error (not a warning, and not a separate CI job to test). Do not suppress NullAway errors without a justification.
Created: Wed Dec 31 11:36:14 GMT 2025 - Last Modified: Thu Dec 11 10:24:40 GMT 2025 - 4K bytes - Click Count (0) -
build-logic/jvm/src/main/kotlin/gradlebuild.jvm-compile.gradle.kts
// it controls the JVM version of the compilation. This allows each source set within a project // to compile to different JVM versions. val jvmCompile = extensions.create<JvmCompileExtension>(JvmCompileExtension.NAME) jvmCompile.compilations.configureEach { // Assume the compilation does not use any workarounds usesJdkInternals = false usesFutureStdlib = false
Created: Wed Dec 31 11:36:14 GMT 2025 - Last Modified: Tue Jun 24 13:46:12 GMT 2025 - 1.4K bytes - Click Count (0) -
docker-buildx.sh
#!/bin/bash set -ex function _init() { ## All binaries are static make sure to disable CGO. export CGO_ENABLED=0 export CRED_DIR="/media/${USER}/minio" ## List of architectures and OS to test coss compilation. SUPPORTED_OSARCH="linux/ppc64le linux/amd64 linux/arm64" remote=$(git remote get-url upstream) if test "$remote" != "******@****.***:minio/minio.git"; then
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Oct 19 08:22:05 GMT 2025 - 1.9K bytes - Click Count (0) -
build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild/AbstractBuildScanInfoCollectingService.kt
/** * A BuildService which monitors a few tasks (in both build-logic and main build) and collects information for Build Scan. * It's currently implemented by two use cases: * 1. Collect cache misses for compilation tasks and publish a `CACHE_MISS` tag for a Build Scan. * 2. Collect failed task paths and display a link which points to the corresponding task in the Build Scan, like `https://ge.gradle.org/s/xxx/console-log?task=yyy`. */
Created: Wed Dec 31 11:36:14 GMT 2025 - Last Modified: Tue Jun 10 05:45:46 GMT 2025 - 2.3K bytes - Click Count (0) -
build-logic/jvm/src/main/kotlin/gradlebuild/jvm/extension/StrictCompileExtension.kt
*/ package gradlebuild.jvm.extension import org.gradle.api.tasks.TaskContainer import org.gradle.api.tasks.compile.JavaCompile import org.gradle.kotlin.dsl.* /** * Strict compilation options honored by [gradlebuild.Strict_compile_gradle]. */ abstract class StrictCompileExtension(val tasks: TaskContainer) { fun ignoreDeprecations() { tasks.withType<JavaCompile>().configureEach {
Created: Wed Dec 31 11:36:14 GMT 2025 - Last Modified: Thu Feb 22 11:17:19 GMT 2024 - 1.4K bytes - Click Count (0)