* However, we can't usually write {@code throw t;} when {@code t} has a static type of {@link
   * Throwable}. But we <i>can</i> write {@code sneakyThrow(t);}.
   *
   * <p>We sometimes also use {@code sneakyThrow} for testing how our code responds to
   * sneaky checked exception.
   *
   * @return never; this method declares a return type of {@link Error} only so that callers can

     */
    public enum RequestType {
        /** Send operation */
        SEND,
        /** Receive operation */
        RECEIVE,
        /** RDMA read operation */
        READ,
        /** RDMA write operation */
        WRITE
    }

    private final long requestId;
    private final RequestType type;
    private final RdmaMemoryRegion memoryRegion;
    private volatile boolean completed;

   * is transmitted. If you cannot ensure that your client and server both support HTTP/2, do not
   * use this feature.
   *
   * ### Duplex APIs
   *
   * With regular request bodies it is not legal to write bytes to the sink passed to
   * [RequestBody.writeTo] after that method returns. For duplex requests bodies that condition is
   * lifted. Such writes occur on an application-provided thread and may occur concurrently with

        }

        @Test
        @DisplayName("Should handle write at buffer boundary")
        void testWriteAtBufferBoundary() {
            byte[] buffer = new byte[100];

            // Try to write at position that would exceed buffer

   * java.nio.file.Files#write(java.nio.file.Path, byte[], java.nio.file.OpenOption...)}.
   *
   * @param from the bytes to write
   * @param to the destination file
   * @throws IOException if an I/O error occurs
   */
  public static void write(byte[] from, File to) throws IOException {
    asByteSink(to).write(from);
  }

  /**

                response.readDataWireFormat(buffer, buffer.length + 1, 10);
            });
        }

        @Test
        @DisplayName("Should handle null buffer in write operations")
        void testWriteOperationsWithNullBuffer() {
            // Write operations return 0 when given null buffer - no exceptions thrown
            assertEquals(0, response.writeSetupWireFormat(null, 0));

     */
    int FILE_NOTIFY_CHANGE_SIZE = 0x00000008;

    /**
     * Any change to the last write-time of files in the watched directory or subtree causes a change notification wait
     * operation to return. The operating system detects a change to the last write-time only when the file is written
     * to the disk. For operating systems that use extensive caching, detection occurs only when the cache is

    assertTrue(sink.wasStreamOpened());
    assertFalse(sink.wasStreamClosed());

    writer.write(STRING);
    writer.close();

    assertTrue(sink.wasStreamClosed());
    assertEquals(STRING, sink.getString());
  }

  public void testWrite_string() throws IOException {
    assertEquals("", sink.getString());
    sink.write(STRING);

    assertTrue(sink.wasStreamOpened() && sink.wasStreamClosed());

 * Lesser General Public License for more details.
 *
 * You should have received a copy of the GNU Lesser General Public
 * License along with this library; if not, write to the Free Software
 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */
package jcifs.internal.smb2;

/**
 * Constants for SMB2/SMB3 protocol.
 *

    /**
     * Test for the writeSetupWireFormat method.
     * It should always return 0.
     */
    @Test
    void testWriteSetupWireFormat() {
        byte[] dst = new byte[10];
        // The method should not write anything and return 0
        assertEquals(0, response.writeSetupWireFormat(dst, 0), "writeSetupWireFormat should return 0.");
    }

    /**
     * Test for the writeParametersWireFormat method.