* </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).

    @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) {

        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

/**
 * Defines the contract for a component responsible for invoking a Maven application
 * using the information provided in an {@link InvokerRequest}. This interface is central
 * to the construction and invocation of Maven commands and builds, and it fully parses arguments.
 *
 * <p>The Invoker is designed to be flexible, allowing for different implementations

### `tf.keras`:

*   Improvements from the Functional API refactoring:
    *   Functional model construction does not need to maintain a global
        workspace graph, removing memory leaks especially when building many
        models or very large models.
    *   Functional model construction should be ~8-10% faster on average.
    *   Functional models can now contain non-symbolic values in their call

labels: [question]
body:
  - type: markdown
    attributes:
      value: |
        Thanks for your interest in FastAPI! 🚀

        Please follow these instructions, fill every question, and do every step. 🙏

        I'm asking this because answering questions and solving problems in GitHub is what consumes most of the time.

    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

        // is a first step. There are several replacements below, in order to normalize
        // the path character before we operate on the string as a regex input, and
        // in order to avoid surprises with the File construction...
        // -------------------------------------------------------------------------------------

        String path = System.getProperty(altLocationSysProp);

        if (path == null || path.isEmpty()) {