import org.jspecify.annotations.NullUnmarked;

/**
 * A generator of {@code TestSuite} instances for testing {@code ByteSink} implementations.
 * Generates tests of all methods on a {@code ByteSink} given various inputs written to it as well
 * as sub-suites for testing the {@code CharSink} view in the same way.
 *
 * @author Colin Decker
 */
@AndroidIncompatible // TODO(b/230620681): Make this available (even though we won't run it).

## Pre-requisites

- Initially, only **one** of the sites added for replication may have data. After site-replication is successfully configured, this data is replicated to the other (initially empty) sites. Subsequently, objects may be written to any of the sites, and they will be replicated to all other sites.

- **Removing a site** is not allowed from a set of replicated sites once configured.
- All sites must be using the **same** external IDP(s) if any.

    void testWriteHeaderWireFormat() {
        packet.type = SessionServicePacket.SESSION_REQUEST;
        packet.length = 0x1234;

        byte[] dst = new byte[10];
        int written = packet.writeHeaderWireFormat(dst, 0);

        assertEquals(4, written);
        assertEquals((byte) SessionServicePacket.SESSION_REQUEST, dst[0]);
        assertEquals((byte) 0x00, dst[1]); // No extended bit
        assertEquals((byte) 0x12, dst[2]);

	// that is considered for inlining, remember this
	// shard value is the value per drive shard it
	// will vary based on the parity that is configured
	// for the STANDARD storage_class.
	// inlining means data and metadata are written
	// together in a single file i.e xl.meta
	InlineBlockEnv = "MINIO_STORAGE_CLASS_INLINE_BLOCK"

	// Supported storage class scheme is EC
	schemePrefix = "EC"

	// Min parity drives
	minParityDrives = 0

        int bodyOffset = headerStart + Smb2Constants.SMB2_HEADER_LENGTH;

        // Encode the full message to set headerStart
        request.encode(buffer, headerStart);

        // Then - verify the body was written correctly
        byte[] pathBytes = TEST_PATH.getBytes(StandardCharsets.UTF_16LE);

        // Verify structure size (9)
        assertEquals(9, SMBUtil.readInt2(buffer, bodyOffset));

    /**
     * Reads up to len bytes of data from the input stream into an array of bytes.
     *
     * @param b the buffer into which the data is read
     * @param off the start offset in array b at which the data is written
     * @param len the maximum number of bytes to read
     * @return the total number of bytes read into the buffer, or -1 if there is no more data
     * @throws IOException if an I/O error occurs
     */
    @Override

        // When
        int bytesWritten = trans.writeParametersWireFormat(dst, 0);

        // Then
        assertEquals(dst.length, bytesWritten, "The number of bytes written should match the expected length.");
        // Check informationLevel
        assertEquals((byte) (informationLevel & 0xFF), dst[0]);
        assertEquals((byte) ((informationLevel >> 8) & 0xFF), dst[1]);

        return shareAccessHint;
    }

    @Override
    protected int writeBytesWireFormat(byte[] dst, int dstIndex) {
        // Lease break notifications are sent by the server, not written by client
        return 0;
    }

    @Override
    protected int readBytesWireFormat(byte[] buffer, int bufferIndex) throws SMBProtocolDecodingException {
        int start = bufferIndex;

    * So, by using FastAPI you are saving development time, bugs, lines of code, and you would probably get the same performance (or better) you would if you didn't use it (as you would have to implement it all in your code)....

- Delivers a complete, valuable change (feature, bug fix, or improvement).
- Has a concise title (e.g., `[S3] Fix bucket policy parsing #1234`) and a summary with context, referencing issues (e.g., `#1234`).
- Contains well-written, logical commits explaining *why* changes were made (e.g., “Add S3 bucket tagging support so that users can organize resources efficiently”).