// Test constructor initializes fields correctly
        LdapUser user = new LdapUser(testEnv, "username");
        assertEquals("username", user.getName());
        assertSame(testEnv, user.getEnvironment());
        assertNull(user.permissions);
    }

    @Test
    public void test_getName() {
        // Test getName returns the correct name
        assertEquals("testuser", ldapUser.getName());

    CacheTesting.drainRecencyQueues(cache);
    assertThat(keySet).contains(0);
  }

  public void testEviction_invalidateAll() {
    // test that .invalidateAll() resets total weight state correctly
    IdentityLoader<Integer> loader = identityLoader();
    LoadingCache<Integer, Integer> cache =
        CacheBuilder.newBuilder().concurrencyLevel(1).maximumSize(10).build(loader);

            assertEquals("Expected structureSize = 4", exception.getMessage());
        }

        @Test
        @DisplayName("Should handle signed byte value correctly")
        void testReadBytesWireFormatSignedByteValue() {
            // Given
            byte[] buffer = new byte[10];
            // Write 4 in little-endian format
            buffer[0] = 0x04;

				entries[i] = ""
				continue
			}
			if hasSuffixByte(entry, SlashSeparatorChar) {
				if strings.HasSuffix(entry, globalDirSuffixWithSlash) {
					// Add without extension so it is sorted correctly.
					entry = strings.TrimSuffix(entry, globalDirSuffixWithSlash) + slashSeparator
					dirObjects[entry] = struct{}{}
					entries[i] = entry
					continue
				}

* The behavior of some watch calls to the server when filtering on fields was incorrect.  If watching objects with a filter, when an update was made that no longer matched the filter a DELETE event was correctly sent.  However, the object that was returned by that delete was not the (correct) version before the update, but instead, the newer version.  That meant the new object was not matched by the filter.  This was a regression from behavior between cached watches on the server side and uncached...

    class ConstantsTests {

        @Test
        @DisplayName("Should have correct FLAGS_NAME_LIST_REFERRAL value")
        void testFlagsNameListReferralConstant() {
            assertEquals(0x0002, Trans2GetDfsReferralResponse.FLAGS_NAME_LIST_REFERRAL);
        }

        @Test
        @DisplayName("Should have correct FLAGS_TARGET_SET_BOUNDARY value")
        void testFlagsTargetSetBoundaryConstant() {

            msrpcShareGetInfo.getSecurity();
        });
    }

    @Test
    void testPtypeAndFlagsValues() {
        // Verify specific flag values are correctly set
        assertEquals(0, msrpcShareGetInfo.getPtype());

        // Check individual flag bits
        int flags = msrpcShareGetInfo.getFlags();
        assertTrue((flags & DcerpcConstants.DCERPC_FIRST_FRAG) != 0);

        assertNotNull(request);
        // SMB2_SET_INFO command value is 0x0011
        assertEquals((short) 0x0011, request.getCommand());

        // Verify file ID is set correctly
        Field fileIdField;
        try {
            fileIdField = Smb2SetInfoRequest.class.getDeclaredField("fileId");
            fileIdField.setAccessible(true);

X25519MLKEM768 by default. The default can be reverted using the
[`tlsmlkem` setting](/pkg/crypto/tls/#Config.CurvePreferences).
This can be useful when dealing with buggy TLS servers that do not handle large records correctly,
causing a timeout during the handshake (see [TLS post-quantum TL;DR fail](https://tldr.fail/)).
Go 1.24 also removed X25519Kyber768Draft00 and the Go 1.23 `tlskyber` setting.

## Edit PR Titles

* Edit the PR title to start with an emoji from [gitmoji](https://gitmoji.dev/).
    * Use the emoji character, not the GitHub code. So, use `🐛` instead of `:bug:`. This is so that it shows up correctly outside of GitHub, for example in the release notes.
    * For translations use the `🌐` emoji ("globe with meridians").