// enclosing, exterior
    assertEquals(range, range.intersection(Range.closed(2, 10)));

    // overlap above
    assertEquals(Range.closed(6, 8), range.intersection(Range.closed(6, 10)));

    // adjacent above
    assertEquals(Range.openClosed(8, 8), range.intersection(Range.openClosed(8, 10)));

    // separate above
    expected =
        assertThrows(

 * way of "cutting" a "number line" (actually of instances of type {@code C}, not necessarily
 * "numbers") into two sections; this can be done below a certain value, above a certain value,
 * below all values or above all values. With this object defined in this way, an interval can
 * always be represented by a pair of {@code Cut} instances.
 *
 * @author Kevin Bourrillion
 */

    // enclosing, exterior
    assertEquals(range, range.intersection(Range.closed(2, 10)));

    // overlap above
    assertEquals(Range.closed(6, 8), range.intersection(Range.closed(6, 10)));

    // adjacent above
    assertEquals(Range.openClosed(8, 8), range.intersection(Range.openClosed(8, 10)));

    // separate above
    expected =
        assertThrows(

// modification, are permitted provided that the following conditions
// are met:
// 1. Redistributions of source code must retain the above copyright
//    notice, this list of conditions and the following disclaimer.
// 2. Redistributions in binary form must reproduce the above copyright
//    notice, this list of conditions and the following disclaimer in the
//    documentation and/or other materials provided with the distribution.

       *
       * - rowEntry isn't cleared except below. If it was cleared below, then either
       *   columnIterator.remove() would have failed above (if the user hasn't called next() since
       *   then) or rowEntry would have been initialized by next() (as discussed above).
       */
      if (requireNonNull(rowEntry).getValue().isEmpty()) {
        rowIterator.remove();
        rowEntry = null;
      }
    }
  }

     * parameter. The pipeType parameter should be at least one of
     * the <code>PIPE_TYPE</code> flags combined with the bitwise OR
     * operator <code>|</code>. See the examples listed above.
     *
     * @param url the SMB URL for the named pipe
     * @param pipeType the type of the pipe
     * @param unshared
     *            whether to use an exclusive connection for this pipe

    @Mock
    private TransactNamedPipeInputStream mockPipeIn;

    @InjectMocks
    private TransTransactNamedPipeResponse response;

    @BeforeEach
    void setUp() {
        // Initialize mocks created above
        MockitoAnnotations.openMocks(this);
        // We need to manually inject the mock as we are not using @InjectMocks on the constructor
        response = new TransTransactNamedPipeResponse(mockPipe);
    }

    /**

 * are provided.
 * <p>
 * The jCIFS client maps DOS error codes to NTSTATUS codes. This means that
 * the user may recieve a different error from a legacy server than that of
 * a newer varient such as Windows NT and above. If you should encounter
 * such a case, please report it to jcifs at samba dot org and we will
 * change the mapping.
 */

public class SmbException extends IOException implements NtStatus, DosError, WinError {

    /**
     * Human-readable error messages corresponding to DOS error codes.
     * Provides descriptive text for each error condition.
     */
    /*
     * These aren't really used by jCIFS--
     * the map above is used to immediately
     * map to NTSTATUS codes.
     */
    /**
     * Human-readable error messages corresponding to DOS error codes.
     * Array of descriptive strings for each DOS error condition.
     */

                    { 0x08bf0002, 0xC0000193 }, { 0x08c00002, 0xC0000070 }, { 0x08c10002, 0xC000006f }, { 0x08c20002, 0xC0000071 }, };

    /* These aren't really used by jCIFS -- the map above is used
     * to immediately map to NTSTATUS codes.
     */
    /**
     * Human-readable error messages corresponding to DOS error codes.
     * Array of descriptive strings for each DOS error condition.
     */