# Build execution model

At the highest level, Gradle's execution model is quite simple:

Below is the protocol in some more detail:

1. The client looks for a compatible idle daemon. If there isn't one, it starts a new daemon.
2. The client connects to the idle daemon and sends it a request to do some work. If the daemon is no longer running, the client starts again.

# See the License for the specific language governing permissions and
# limitations under the License.
# ==============================================================================
"""
Top-level module of TensorFlow. By convention, we refer to this module as
`tf` instead of `tensorflow`, following the common practice of importing
TensorFlow via the command `import tensorflow as tf`.

     1. plugin goal execution in a child is usually simply appended (at end): you can't try to insert in the middle of pre-existing inherited executions,

     2. append happens at plugin level first, then goal level, independently from phases.
        This means for example that adding pluginA:goal2 to pre-existing (pluginA:goal1, pluginB:goal) will lead to (pluginA:goal1, pluginA:goal2, pluginB:goal)

     */
    public ExecJob logFilePath(final String logFilePath) {
        this.logFilePath = logFilePath;
        return this;
    }

    /**
     * Sets the log level for this job execution.
     *
     * @param logLevel the log level (e.g., DEBUG, INFO, WARN, ERROR)
     * @return this ExecJob instance for method chaining
     */
    public ExecJob logLevel(final String logLevel) {
        this.logLevel = logLevel;

import okhttp3.Call
import okhttp3.OkHttpClient
import okhttp3.Response
import okhttp3.sse.internal.RealEventSource

object EventSources {
  @Deprecated(
    message = "required for binary-compatibility!",
    level = DeprecationLevel.HIDDEN,
  )
  @JvmStatic
  fun createFactory(client: OkHttpClient) = createFactory(client as Call.Factory)

  @JvmStatic
  fun createFactory(callFactory: Call.Factory): EventSource.Factory =

 * Provides common functionality for various SMB2/SMB3 file system information classes
 * used in query file system information operations, with constants for information levels.
 *
 * @author mbechler
 */
public interface FileSystemInformation extends Decodable {

    /**
     * SMB information allocation constant.
     */
    byte SMB_INFO_ALLOCATION = -1;

    /**

-   [guava-discuss: For open-ended questions and discussion](https://groups.google.com/group/guava-discuss)

## IMPORTANT WARNINGS

1.  APIs marked with the `@Beta` annotation at the class or method level are
    subject to change. They can be modified in any way, or even removed, at any
    time. If your code is a library itself (i.e., it is used on the CLASSPATH of

  TLS_1_0("TLSv1"), // 1999.
  SSL_3_0("SSLv3"), // 1996.
  ;

  @JvmName("-deprecated_javaName")
  @Deprecated(
    message = "moved to val",
    replaceWith = ReplaceWith(expression = "javaName"),
    level = DeprecationLevel.ERROR,
  )
  fun javaName(): String = javaName

  companion object {
    @JvmStatic
    fun forJavaName(javaName: String): TlsVersion =
      when (javaName) {
        "TLSv1.3" -> TLS_1_3

                    \$(document).ready(function () {
                        const level = \$("#filter-preset")[0].value;
                        \$("a[role='menuitem']").each (function() {
                            if (this.text === level) {
                                this.click();
                            }
                        });

## How to enable Fan-Out Uploads ?

Fan-Out uploads are automatically enabled if `x-minio-fanout-list` form-field is provided with the PostUpload API, to keep things simple higher level APIs are provided in our SDKs for example in `minio-go` SDK:

```
PutObjectFanOut(ctx context.Context, bucket string, fanOutContent io.Reader, fanOutReq minio.PutObjectFanOutRequest) ([]minio.PutObjectFanOutResponse, error)