import jcifs.internal.util.SMBUtil;
import jcifs.util.Hexdump;

/**
 * SMB2 Oplock Break notification message. This server-initiated message notifies the client
 * that an opportunistic lock must be broken due to conflicting access from another client.
 *
 * @author mbechler
 *
 */
public class Smb2OplockBreakNotification extends ServerMessageBlock2Response {

    private byte oplockLevel;
    private byte[] fileId;

    /**

 * This form extends CreateForm to include fields necessary for updating existing group entries,
 * including tracking information for optimistic locking and audit trails.
 * Groups are used to organize users and define access permissions.
 *
 */
public class EditForm extends CreateForm {

    /**
     * Creates a new EditForm instance.
     */
    public EditForm() {
        super();
    }

    /**

 */
package jcifs.internal.fscc;

import jcifs.internal.SMBProtocolDecodingException;
import jcifs.internal.util.SMBUtil;

/**
 * File System Control Code (FSCC) structure for File Internal Information.
 * Provides access to the file's internal index number, which is a unique identifier
 * assigned by the file system for internal tracking and reference purposes.
 *
 * @author mbechler
 */

            assertArrayEquals(new short[] { 65, 66, 67 }, unicodeString.buffer);
        }

        @Test
        @DisplayName("Should test unicode string encoding without deferred buffer access")
        void testUnicodeStringEncodeStructure() throws NdrException {
            // Given: A unicode string with values that won't use deferred encoding
            rpc.unicode_string unicodeString = new rpc.unicode_string();

# ADR-0004 - Use a platform-oriented architecture for Gradle

## Status

- ACCEPTED on 2024-02-07

## Context

The Gradle code base is essentially a large monolith, without strong internal boundaries.
This has a number of negative effects on productivity, including:

- Unclear ownership of code.
- Difficult to focus on one particular area.
- Unintended coupling between areas of the code, including tests.

## Decision

# ADR-0008 - Use NullAway for null checking

## Status

- ACCEPTED on 2025-08-06

## Context

Our codebase uses `null` extensively to represent an absence of value or optionality of the argument.
We utilize nullness annotations in Java code and somewhat rely on IDE warnings to guide us.
However, the Java code we have is not fully annotated, which causes several consequences:
* IDE warnings can be misleading

        SmbFilenameFilter filter = (dir, n) -> n == null;

        boolean result = filter.accept(mockDir, name);

        if (name == null) {
            assertTrue(result, "Null name should be accepted by this filter");
        } else {
            assertFalse(result, "Non-null names should be rejected by this filter");
        }
        verifyNoInteractions(mockDir);
    }

    /**

* Traiter des données :
    * Par exemple, si vous recevez un fichier qui doit passer par un traitement lent, vous pouvez retourner une réponse « Accepted » (HTTP 202) puis faire le traitement en arrière-plan.

## Utiliser `BackgroundTasks` { #using-backgroundtasks }

 * </ul>
 *
 * <p>The main purpose of {@link #addListener addListener} is to support this chaining. You will
 * rarely use it directly, in part because it does not provide direct access to the {@code Future}
 * result. (If you want such access, you may prefer {@link Futures#addCallback
 * Futures.addCallback}.) Still, direct {@code addListener} calls are occasionally useful:
 *
 * {@snippet :
 * final String name = ...;

        assertFalse(provider.isUseTimeZoneHandling());
    }

    // Test isAcceptCookieTimeZone() method
    @Test
    public void test_isAcceptCookieTimeZone() {
        // Verify that cookie time zone is not accepted
        assertFalse(provider.isAcceptCookieTimeZone());
    }

    // Test findBusinessTimeZone() method
    @Test
    public void test_findBusinessTimeZone() {
        // Setup