// Test successful PAC creation with mocked Pac construction
    @Test
    void testConstructorSuccess() throws PACDecodingException {
        // Setup key
        byte[] keyBytes = new byte[32];
        KerberosKey kdcKey = new KerberosKey(null, keyBytes, PacSignature.HMAC_SHA1_96_AES256, 1);
        keys.put(PacSignature.ETYPE_AES256_CTS_HMAC_SHA1_96, kdcKey);

        // Mock Pac construction to bypass complex validation

        // Note: Mockito cannot directly verify super constructor calls.
        // We assume if the object is created, the super constructor was called.
        // We can verify the state of the object after construction.

        // Verify ptype and flags are set correctly
        assertEquals(0, policy.getPtype(), "ptype should be 0");

        return Stream.of(Arguments.of((String) null), Arguments.of(""));
    }

    /**
     * Validate message+cause constructor and that no interaction with cause occurs during construction.
     */
    @Test
    @DisplayName("String+Throwable ctor: sets message, cause and unsuccessful status")
    void messageAndCauseConstructor_setsFields(@Mock Throwable mockCause) {
        // Arrange

    @Test
    @DisplayName("constructor accepts null andx")
    void constructorWithNullAndx() {
        SmbComLogoffAndX msg = new SmbComLogoffAndX(null);
        assertNotNull(msg, "Message must not be null after construction");
    }

    @ParameterizedTest
    @ValueSource(ints = { 0, 1, 5, -1, 10 })
    @DisplayName("writeParameterWordsWireFormat always returns 0")
    void writeParameterWordsWireFormatReturnsZero(int index) {

 * </ul>
 *
 * <p>Disadvantages compared to {@code long[]}:
 *
 * <ul>
 *   <li>Memory footprint has a fixed overhead (about 24 bytes per instance).
 *   <li><i>Some</i> construction use cases force the data to be copied (though several construction
 *       APIs are offered that don't).
 *   <li>Can't be passed directly to methods that expect {@code long[]} (though the most common
 *       utilities do have replacements here).

 * </ul>
 *
 * <p>Disadvantages compared to {@code int[]}:
 *
 * <ul>
 *   <li>Memory footprint has a fixed overhead (about 24 bytes per instance).
 *   <li><i>Some</i> construction use cases force the data to be copied (though several construction
 *       APIs are offered that don't).
 *   <li>Can't be passed directly to methods that expect {@code int[]} (though the most common
 *       utilities do have replacements here).

    void testConstructorSetsCommand() {
        SmbComClose close = new SmbComClose(1, 12345L);
        assertEquals(SMB_COM_CLOSE, close.command, "command should be SMB_COM_CLOSE after construction");
    }

    /**
     * Verify that writeParameterWordsWireFormat writes the file id and the
     * unsigned time correctly.  The last write time is zero which should be

        assertNotNull(ex.toString(), "toString should be non-null");
        ex.getMessage(); // don't assert content to avoid implementation assumptions

        // Verify no interactions happened with the mocked cause during construction/access
        verifyNoInteractions(mockCause);
    }

    @Test
    @DisplayName("Cause-only constructor with null: null cause maintained")
    void causeOnlyConstructor_acceptsNull() {
        // Arrange & Act

    MemoizingSupplier(Supplier<T> delegate) {
      this.delegate = checkNotNull(delegate);
    }

    @Override
    @ParametricNullness
    // We set the field only once (during construction or deserialization).
    @SuppressWarnings("SynchronizeOnNonFinalField")
    public T get() {
      // A 2-field variant of Double Checked Locking.
      if (!initialized) {
        synchronized (lock) {

 *
 * <p><b>Warning:</b> {@code ArrayTable} is rarely the {@link Table} implementation you want. First,
 * it requires that the complete universe of rows and columns be specified at construction time.
 * Second, it is always backed by an array large enough to hold a value for every possible
 * combination of row and column keys. (This is rarely optimal unless the table is extremely dense.)