- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 984 for executed (0.05 sec)
-
logger/slog.go
l.log(ctx, slog.LevelError, "SQL executed", slog.Attr{ Key: "trace", Value: slog.GroupValue(fields...), }) case l.SlowThreshold != 0 && elapsed > l.SlowThreshold: l.log(ctx, slog.LevelWarn, "SQL executed", slog.Attr{ Key: "trace", Value: slog.GroupValue(fields...), }) case l.LogLevel >= Info: l.log(ctx, slog.LevelInfo, "SQL executed", slog.Attr{ Key: "trace",
Registered: Sun Dec 28 09:35:17 UTC 2025 - Last Modified: Thu Oct 30 10:56:26 UTC 2025 - 2.9K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/Dispatcher.kt
import okhttp3.internal.unmodifiable /** * Policy on when async requests are executed. * * Each dispatcher uses an [ExecutorService] to run calls internally. If you supply your own * executor, it should be able to run [the configured maximum][maxRequests] number of calls * concurrently. */ class Dispatcher() { /** * The maximum number of requests to execute concurrently. Above this requests queue in memory,
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Tue Oct 07 14:16:22 UTC 2025 - 9.9K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/concurrent/Task.kt
* limitations under the License. */ package okhttp3.internal.concurrent /** * A unit of work that can be executed one or more times. * * Recurrence * ---------- * * Tasks control their recurrence schedule. The [runOnce] function returns -1L to signify that the * task should not be executed again. Otherwise it returns a delay until the next execution. *
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Fri Dec 27 13:39:56 UTC 2024 - 2.4K bytes - Viewed (0) -
impl/maven-core/src/main/java/org/apache/maven/lifecycle/internal/concurrent/BuildPlanExecutor.java
import static org.apache.maven.lifecycle.internal.concurrent.BuildStep.TEARDOWN; /** * Executes the Maven build plan in a concurrent manner, handling the lifecycle phases and plugin executions. * This executor implements a weave-mode build strategy, where builds are executed phase-by-phase rather than * project-by-project. * * <h2>Key Features:</h2> * <ul>
Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Thu Oct 16 06:12:36 UTC 2025 - 55.1K bytes - Viewed (0) -
docs/en/docs/advanced/advanced-dependencies.md
Using `Depends(scope="function")`, the exit code after `yield` is executed right after the *path operation function* is finished, before the response is sent back to the client. And when using `Depends(scope="request")` (the default), the exit code after `yield` is executed after the response is sent.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Thu Nov 13 07:37:15 UTC 2025 - 9.1K bytes - Viewed (0) -
impl/maven-core/src/main/java/org/apache/maven/lifecycle/internal/PhaseExecutionPoint.java
* the phase. Any {@link #AFTER} phases will still be executed. */ AT(""), /** * Guaranteed execution dynamic phases on completion of the static phase. All {@code #AFTER} dynamic phases will * be executed provided at least one {@link #BEFORE} or {@link #AT} dynamic phase has started execution. */ AFTER("after:");Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 1.8K bytes - Viewed (0) -
docs/en/docs/tutorial/dependencies/dependencies-with-yield.md
Only the code prior to and including the `yield` statement is executed before creating a response: {* ../../docs_src/dependencies/tutorial007_py39.py hl[2:4] *} The yielded value is what is injected into *path operations* and other dependencies: {* ../../docs_src/dependencies/tutorial007_py39.py hl[4] *} The code following the `yield` statement is executed after the response:Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 12.9K bytes - Viewed (0) -
build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild.cache-miss-monitor.gradle.kts
import java.io.Serializable import java.util.concurrent.atomic.AtomicBoolean /** * Register a build service that monitors a list of tasks and reports CACHE_MISS if they're actually executed. */ if (buildCacheEnabled()) { registerBuildScanInfoCollectingService(CacheMissMonitorBuildService::class.java, ::isCacheMissMonitoredTask) { gradleRootProject, cacheMissInBuildLogic, cacheMissInMainBuild ->
Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Fri Apr 11 20:57:49 UTC 2025 - 4.8K bytes - Viewed (0) -
docs/en/docs/tutorial/debugging.md
{* ../../docs_src/debugging/tutorial001_py39.py hl[1,15] *} ### About `__name__ == "__main__"` { #about-name-main } The main purpose of the `__name__ == "__main__"` is to have some code that is executed when your file is called with: <div class="termy"> ```console $ python myapp.py ``` </div> but is not called when another file imports it, like in: ```Python from myapp import app ```Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 17 20:41:43 UTC 2025 - 2.4K bytes - Viewed (0) -
impl/maven-core/src/main/java/org/apache/maven/project/collector/MultiModuleCollectionStrategy.java
import org.eclipse.aether.transfer.ArtifactNotFoundException; import org.slf4j.Logger; import org.slf4j.LoggerFactory; /** * Strategy for collecting Maven projects from the multi-module project root, even when executed in a submodule. */ @Named("MultiModuleCollectionStrategy") @Singleton public class MultiModuleCollectionStrategy implements ProjectCollectionStrategy {Registered: Sun Dec 28 03:35:09 UTC 2025 - Last Modified: Sat Apr 05 11:52:05 UTC 2025 - 9.1K bytes - Viewed (0)