*     of this class typically expect for instances to have a non-null cause. At the moment, you
   *     can <i>usually</i> still preserve behavior by passing an explicit {@code null} cause. Note,
   *     however, that passing an explicit {@code null} cause prevents anyone from calling {@link
   *     #initCause} later, so it is not quite equivalent to using a constructor that omits the
   *     cause.
   */

 * It implements the Closeable interface to ensure that resources are properly released.
 *
 * <p>This class supports two types of content caching:
 * <ul>
 *   <li>In-memory caching using a byte array</li>
 *   <li>File-based caching using a File object</li>
 * </ul>
 *
 * <p>When an instance of ContentCache is created with a byte array, the content is cached in memory.

#
# Maven Cache Configuration
#
# Controls caching behavior for different request types during Maven builds.
# Format: RequestType { scope:SCOPE ref:REFERENCE_TYPE }
#
# SCOPE OPTIONS:
#   session - Cache for entire Maven session (all modules in multi-module build)
#   request - Cache only for current request + its child requests
#   none    - Disable caching entirely
#
# REFERENCE OPTIONS:

   *     of this class typically expect for instances to have a non-null cause. At the moment, you
   *     can <i>usually</i> still preserve behavior by passing an explicit {@code null} cause. Note,
   *     however, that passing an explicit {@code null} cause prevents anyone from calling {@link
   *     #initCause} later, so it is not quite equivalent to using a constructor that omits the
   *     cause.
   */

        int key1 = rand.nextInt();
        // flip input bit for key2
        int key2 = key1 ^ (1 << i);
        // get hashes
        int hash1 = function.hashInt(key1).asInt();
        int hash2 = function.hashInt(key2).asInt();
        // test whether the hash values have same output bits
        same |= ~(hash1 ^ hash2);
        // test whether the hash values have different output bits

        // Should return true when read caching is enabled
        assertTrue(DirectoryLeaseState.canCacheEnumeration(Smb2LeaseState.SMB2_LEASE_READ_CACHING));
        assertTrue(DirectoryLeaseState.canCacheEnumeration(DirectoryLeaseState.DIRECTORY_READ_HANDLE));
        assertTrue(DirectoryLeaseState.canCacheEnumeration(DirectoryLeaseState.DIRECTORY_FULL));

        // Should return false when read caching is not enabled

        assertEquals(0x05, Smb2LeaseState.SMB2_LEASE_READ_WRITE);
        assertEquals(0x07, Smb2LeaseState.SMB2_LEASE_FULL);
    }

    @Test
    @DisplayName("Should detect read caching correctly")
    void testHasReadCaching() {
        assertTrue(Smb2LeaseState.hasReadCaching(Smb2LeaseState.SMB2_LEASE_READ_CACHING));
        assertTrue(Smb2LeaseState.hasReadCaching(Smb2LeaseState.SMB2_LEASE_READ_HANDLE));

    /**
     * Share flag indicating manual caching of documents.
     */
    public static final int SMB2_SHAREFLAG_MANUAL_CACHING = 0x0;
    /**
     * Share flag indicating automatic caching of documents.
     */
    public static final int SMB2_SHAREFLAG_AUTO_CACHING = 0x10;
    /**
     * Share flag indicating automatic caching of programs and documents.
     */

#   re-running tests. However, note that:
#
#    - New environments like new CUDA versions, changes to manylinux,
#      compilers, etc. can cause undefined behavior such as build failures
#      or tests passing incorrectly.
#    - Automatic LLVM updates are known to extend build time even with
#      the cache; this is unavoidable.
export TFCI=py311,linux_x86,public_cache,disk_cache

# Recommended: Configure Docker. (Linux only)

        int key1 = rand.nextInt();
        // flip input bit for key2
        int key2 = key1 ^ (1 << i);
        // get hashes
        int hash1 = function.hashInt(key1).asInt();
        int hash2 = function.hashInt(key2).asInt();
        // test whether the hash values have same output bits
        same |= ~(hash1 ^ hash2);
        // test whether the hash values have different output bits