* for document data. This class wraps an existing map and provides custom behavior
 * for the entrySet method to ensure language fields appear first in iteration order.
 * Used throughout the Fess search system for document data manipulation.
 *
 */
public class DocMap implements Map<String, Object> {

    /** The key used for language field identification */

import java.util.Map;
import java.util.Objects;
import org.jspecify.annotations.Nullable;

/**
 * Used to represent the order of elements in a data structure that supports different options for
 * iteration order guarantees.
 *
 * <p>Example usage:
 *
 * {@snippet :
 * MutableGraph<Integer> graph =
 *     GraphBuilder.directed().nodeOrder(ElementOrder.<Integer>natural()).build();
 * }
 *

import java.util.Map;
import java.util.Objects;
import org.jspecify.annotations.Nullable;

/**
 * Used to represent the order of elements in a data structure that supports different options for
 * iteration order guarantees.
 *
 * <p>Example usage:
 *
 * {@snippet :
 * MutableGraph<Integer> graph =
 *     GraphBuilder.directed().nodeOrder(ElementOrder.<Integer>natural()).build();
 * }
 *

it in plaintext (no KMS) or re-encrypts using the KMS.

> Is this change backward compatible? Will it break my setup?

This change is not backward compatible for all setups. In particular, the native
Hashicorp Vault integration - which has been deprecated already - won't be
supported anymore. KES is now mandatory if a third-party KMS should be used.

Further, since the configuration data is encrypted with the KMS, the KMS

            assertEquals(0, in.skip(0));
            assertEquals(0, in.skip(-1));
            assertEquals(5, in.skip(5));
        }
    }

    @Nested
    @DisplayName("SMB1 interactions")
    class Smb1Behavior {

        @Test
        @DisplayName("Named pipe: broken pipe maps to -1")
        void namedPipeBrokenPipeReturnsMinusOne() throws Exception {

import jcifs.internal.NotifyResponse;
import jcifs.internal.smb1.trans.nt.NtTransNotifyChange;
import jcifs.internal.smb2.notify.Smb2ChangeNotifyRequest;

/**
 * Tests for SmbWatchHandleImpl focusing on behavior and interactions.
 */
@ExtendWith(MockitoExtension.class)
class SmbWatchHandleImplTest {

    @Mock
    SmbFileHandleImpl handle;

    @Mock
    SmbTreeHandleImpl tree;

                int result = echoRequest.readBytesWireFormat(null, 0);
                assertEquals(0, result);
            });
        }
    }

    @Nested
    @DisplayName("Integration Tests")
    class IntegrationTests {

        @Test
        @DisplayName("Should work as complete request-response cycle")
        void testCompleteRequestResponseCycle() {
            // Create request

                cwd,
                userHome,
                List.of("eu.maveniverse.maven.plugins:toolbox:" + Environment.TOOLBOX_VERSION + ":dump"),
                List.of("--force-interactive"));

        String log = logs.get("eu.maveniverse.maven.plugins:toolbox:" + Environment.TOOLBOX_VERSION + ":dump");
        assertTrue(log.contains("https://repo1.maven.org/maven2"), log);

            when(mockMd5.clone()).thenThrow(new CloneNotSupportedException("Test Clone Not Supported"));

            assertThrows(IllegalStateException.class, originalHmac::clone);
        }
    }

    // Integration test with actual MD5 to verify HMAC calculation logic
    @Test
    void testHMACT64WithActualMD5() throws NoSuchAlgorithmException {
        // This test uses a real MD5 instance to verify the HMAC calculation logic

That's the benefit of standards...

///

## See it in action { #see-it-in-action }

Open the interactive docs: <a href="http://127.0.0.1:8000/docs" class="external-link" target="_blank">http://127.0.0.1:8000/docs</a>.

### Authenticate { #authenticate }

Click the "Authorize" button.

Use the credentials: