if ! git clone --quiet https://github.com/minio/mc "$MC_BUILD_DIR"; then
		echo "failed to download https://github.com/minio/mc"
		purge "${MC_BUILD_DIR}"
		exit 1
	fi

	(cd "${MC_BUILD_DIR}" && go build -o "${WORK_DIR}/mc")

	# remove mc source.
	purge "${MC_BUILD_DIR}"

	shred -n 1 -s 1M - 1>"$FILE_1_MB" 2>/dev/null
	shred -n 1 -s 65M - 1>"$FILE_65_MB" 2>/dev/null

Rene Groeschke <******@****.***> 1622539170 +0200

Rene Groeschke <******@****.***> 1622539170 +0200

Rene Groeschke <******@****.***> 1622539170 +0200

Rene Groeschke <******@****.***> 1622539170 +0200

Rene Groeschke <******@****.***> 1622539170 +0200

Rene Groeschke <******@****.***> 1622539170 +0200

        return collect(
                DependencyResolverRequest.build(session, DependencyResolverRequest.RequestType.COLLECT, root, scope));
    }

    /**
     * Collects the transitive dependencies of some artifacts and builds a dependency graph for the given path scope.
     * Note that this operation is only concerned about determining the coordinates of the transitive dependencies and

# 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.

      }

      ImmutableRangeSet<Integer> built = builder.build();
      assertEquals(mutable, built);
      assertEquals(ImmutableRangeSet.copyOf(mutable), built);
      assertEquals(mutable.complement(), built.complement());

      for (int i = 0; i <= 11; i++) {
        assertEquals(mutable.contains(i), built.contains(i));
      }

      SerializableTester.reserializeAndAssert(built);