}
  }

  /**
   * We had a bug where a custom `ResponseBody` interacted poorly with `Response.trailers()`.
   * Confirm custom trailers can be read without even accessing the response body.
   */
  @Test
  fun customTrailersDoNotUseResponseBody() {
    val response =
      Response
        .Builder()

        // When & Then - Will throw SMBProtocolDecodingException when trying to read beyond buffer
        assertThrows(ArrayIndexOutOfBoundsException.class, () -> {
            response.readBytesWireFormat(buffer, offset);
        });
    }

    @DisplayName("Should read at different offsets correctly")
    @ParameterizedTest
    @ValueSource(ints = { 0, 10, 50, 100, 200 })

// The result is unaffected by any method calls except [Reader.Reset].
func (r *Reader) Size() int64 { return int64(len(r.s)) }

// Read implements the [io.Reader] interface.
func (r *Reader) Read(b []byte) (n int, err error) {
	if r.i >= int64(len(r.s)) {
		return 0, io.EOF
	}
	r.prevRune = -1
	n = copy(b, r.s[r.i:])
	r.i += int64(n)
	return
}

If something seems interesting and useful to your project, go ahead and check it, but otherwise, you might probably just skip them.

/// tip

If you want to **learn FastAPI** in a structured way (recommended), go and read the [Tutorial - User Guide](../tutorial/index.md){.internal-link target=_blank} chapter by chapter instead.

            SMBUtil.writeInt2(4, buffer, start);
            Smb2LogoffResponse resp = newResponse();

            // Act
            int read = resp.readBytesWireFormat(buffer, start);

            // Assert
            assertEquals(4, read, "Should return the fixed structure size (4)");
        }

        @ParameterizedTest
        @ValueSource(ints = { 0, 1, 7 })

import org.apache.maven.api.model.Model;
import org.apache.maven.api.services.Source;

/**
 * The {@code ModelParser} interface is used to locate and read {@link Model}s from the file system.
 * This allows plugging in additional syntaxes for the main model read by Maven when building a project.
 *
 * @since 4.0.0
 */
@Experimental
@Consumer
@Named
public interface ModelParser extends SpiService {

    /**

        assertEquals(TransPeekNamedPipeResponse.STATUS_LISTENING, response.getStatus());
        // Middle bytes were read but not used
    }

    @Test
    @DisplayName("Test consecutive reads update state correctly")
    void testConsecutiveReads() {
        // First read
        byte[] buffer1 = new byte[10];
        SMBUtil.writeInt2(100, buffer1, 0);
        SMBUtil.writeInt2(0, buffer1, 2);

### Certificate Directory

TLS certificates by default are expected to be stored under ``${HOME}/.minio/certs`` directory. You need to place certificates here to enable `HTTPS` based access. Read more about [How to secure access to MinIO server with TLS](https://docs.min.io/community/minio-object-store/operations/network-encryption.html).

Following is a sample directory structure for MinIO server with TLS certificates.

        assertEquals(0, response.writeParametersWireFormat(buffer, 0));
        assertEquals(0, response.writeDataWireFormat(buffer, 0));
    }

    @Test
    @DisplayName("All read methods should consistently return 0")
    void testAllReadMethodsReturnZero() {
        // Arrange
        byte[] buffer = new byte[100];

        // Act & Assert

            assertNotNull(result);

            switch (type) {
            case METADATA:
                assertEquals("metadata", result);
                break;
            case LOGOUT:
                assertEquals("logout", result);
                break;
            default:
                fail("Unexpected enum value: " + type);
            }
        }
    }