related to Product X, those performance claims and warranties are such Commercial
Contributor's responsibility alone. Under this section, the Commercial Contributor
would have to defend claims against the other Contributors related to those
performance claims and warranties, and if a court requires any other Contributor
to pay any damages as a result, the Commercial Contributor must pay those
damages.

   5. NO WARRANTY

import org.jspecify.annotations.Nullable;

/**
 * A {@link SortedMultiset} whose contents will never change, with many other important properties
 * detailed at {@link ImmutableCollection}.
 *
 * <p><b>Warning:</b> as with any sorted collection, you are strongly advised not to use a {@link
 * Comparator} or {@link Comparable} type whose comparison behavior is <i>inconsistent with

    void testReadWriteMethodsReturnValues() {
        SmbComClose close = new SmbComClose(10, 5000L);
        assertEquals(0, close.readParameterWordsWireFormat(new byte[10], 0));
        assertEquals(0, close.readBytesWireFormat(new byte[10], 0));
        assertEquals(0, close.writeBytesWireFormat(new byte[10], 0));
        assertEquals(6, close.writeParameterWordsWireFormat(new byte[10], 0));
    }

    /**

        cos.close();
    }

    @Test
    public void testExactThreshold() throws IOException {
        // Writing exactly threshold bytes should stay in memory
        ContentOutputStream cos = new ContentOutputStream(5, Curl.tmpDir);
        cos.write(new byte[] { 0, 1, 2, 3, 4 });
        assertTrue(cos.isInMemory());
        assertFalse(cos.done);
        cos.close();
    }

    @Test

import okhttp3.internal.toImmutableList
import okhttp3.tls.internal.TlsUtil.newKeyManager
import okhttp3.tls.internal.TlsUtil.newTrustManager

/**
 * Certificates to identify which peers to trust and also to earn the trust of those peers in kind.
 * Client and server exchange these certificates during the handshake phase of a TLS connection.
 *
 * ### Server Authentication
 *

> certs from the server certificate chain, this is mainly to add simplicity of setup. However if you wish to terminate
> TLS certificates via a different domain for your FTP servers you may choose the above command line options.


### Custom Algorithms (SFTP)

Custom algorithms can be specified via command line parameters.
Algorithms are comma separated. 

        // Mock close success for the first call
        doAnswer(invocation -> {
            MsrpcSamrCloseHandle rpc = invocation.getArgument(0);
            rpc.retval = 0;
            return null;
        }).when(mockDcerpcHandle).sendrecv(any(MsrpcSamrCloseHandle.class));

        // First close call
        aliasHandle.close();

        // Act: Call close again
        aliasHandle.close();

        // Simulate successful close
        doAnswer(invocation -> {
            MsrpcSamrCloseHandle rpc = invocation.getArgument(0);
            rpc.retval = 0;
            return null;
        }).when(mockDcerpcHandle).sendrecv(any(MsrpcSamrCloseHandle.class));

        // First close call
        handle.close();

        // Act
        // Second close call
        handle.close();

          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not

        protected Credentials getDefaultCredentials() {
            return defaultCreds;
        }

        @Override
        public boolean close() throws CIFSException {
            closeCalled = true;
            // Call super.close() to ensure the shutdown hook is removed
            return super.close();
        }

        public boolean isCloseCalled() {
            return closeCalled;
        }

        @Override