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

        assertEquals(Trans2FindFirst2.LIST_SIZE, next.maxDataCount, "Max data count should use LIST_SIZE");
        assertEquals((byte) 0x00, next.maxSetupCount, "Max setup count must be 0");

        // Information level defaults to BOTH_DIRECTORY_INFO (0x104) — check via parameters encoding
        byte[] buf = new byte[2 + 2 + 2 + 4 + 2 + filename.length() + 1];
        int n = next.writeParametersWireFormat(buf, 0);

import jcifs.internal.util.SMBUtil;

/**
 * SMB1 COM_LOCKING_ANDX command implementation.
 *
 * This command locks or unlocks byte ranges within a file. It can also
 * be used to break oplocks and change oplock levels.
 *
 * @author mbechler
 */
public class SmbComLockingAndX extends AndXServerMessageBlock {

    private int fid;
    private byte typeOfLock;
    private byte newOpLockLevel;
    private long timeout;

        return type2;
    }

    /**
     * Helper method to create a mock context with specific LanMan compatibility level
     */
    private CIFSContext createMockContextWithLanManCompat(int level) {
        CIFSContext mockCtx = mock(CIFSContext.class);
        Configuration mockConfig = mock(Configuration.class);

### Minor changes to the library {#minor_library_changes}

#### go/types

The `Var.Kind` method returns an enumeration of type `VarKind` that
classifies the variable (package-level, local, receiver, parameter,
result, or struct field). See issue #70250.

Callers of `NewVar` or `NewParam` are encouraged to call `Var.SetKind`

    /**
     * Gets the problems that were encountered during the settings building. Note that only problems of severity
     * {@link BuilderProblem.Severity#WARNING} and below are reported here. Problems with a higher severity level cause
     * the settings builder to fail with a {@link SettingsBuilderException}.
     *
     * @return the problems that were encountered during the settings building, can be empty but never {@code null}
     */
    @Nonnull

    /**
     * Gets the problems that were encountered during the settings building. Note that only problems of severity
     * {@link BuilderProblem.Severity#WARNING} and below are reported here. Problems with a higher severity level cause
     * the settings builder to fail with a {@link ToolchainsBuilderException}.
     *
     * @return the problems that were encountered during the settings building, can be empty but never {@code null}
     */

- Write and Read quorum are required to be satisfied only across the erasure set for an object. Healing is also done per object within the erasure set which contains the object.

    See the License for the specific language governing permissions and
    limitations under the License.
 -->

# Apache Lucene and Solr have separate repositories now!

Solr has become a top-level Apache project and main line 
development for Lucene and Solr is happening in each 
project's git repository now:

- Lucene: <https://gitbox.apache.org/repos/asf/lucene.git>

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