// Close the stream
        outputStream.close();

        // When & Then - after close, tmp is null so write(int) will throw NullPointerException
        // This is the actual behavior of the implementation
        assertThrows(NullPointerException.class, () -> outputStream.write(65));
    }

    @Test
    void testWriteNullArray() throws CIFSException {
        // Given

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

        assertFalse(result, "Filter should reject any provided name");
        verifyNoInteractions(mockDir);
    }

    /**
     * Edge: name-based filter behavior for diverse inputs.
     */
    @ParameterizedTest
    @DisplayName("name-based filter matches .txt case-insensitively")

    `LSTMStateTuple`. The new behavior leads to proper dropout behavior for
    LSTMs and stacked LSTMs. This bug fix follows recommendations from published
    literature, but is a behavioral change. State dropout behavior may be
    customized via the new `dropout_state_filter_visitor` argument.
*   Removed `tf.contrib.training.python_input`. The same behavior, in a more

 *
 * <p><b>Warning:</b> The methods of {@code ForwardingList} forward <b>indiscriminately</b> to the
 * methods of the delegate. For example, overriding {@link #add} alone <b>will not</b> change the
 * behavior of {@link #addAll}, which can lead to unexpected behavior. In this case, you should
 * override {@code addAll} as well, either providing your own implementation, or delegating to the
 * provided {@code standardAddAll} method.
 *

 * methods to modify the behavior of the backing set as desired per the <a
 * href="http://en.wikipedia.org/wiki/Decorator_pattern">decorator pattern</a>.
 *
 * <p><b>Warning:</b> The methods of {@code ForwardingSet} forward <b>indiscriminately</b> to the
 * methods of the delegate. For example, overriding {@link #add} alone <b>will not</b> change the

   *
   * <p><b>Warning: do not depend</b> on the behavior of this method.
   *
   * <p>Historically, {@code Predicate} instances in this library have implemented this method to
   * recognize certain cases where distinct {@code Predicate} instances would in fact behave
   * identically. However, as code migrates to {@code java.util.function}, that behavior will
   * disappear. It is best not to depend on it.
   */
  @Override

          # ISSUES (deactivated) ----------------------------------------------
          # This workflow should touch no issues, so times are set to -1
          # (see actions/stale documentation for the behavior)
          days-before-issue-stale: -1
          stale-issue-label: stale
          stale-issue-message: >
            **BUG!** This issue should not be marked stale by the "stale" workflow.

 * object is equal to the original.
 *
 * <p><b>GWT warning:</b> Under GWT, both methods simply returns their input, as proper GWT
 * serialization tests require more setup. This no-op behavior allows test authors to intersperse
 * {@code SerializableTester} calls with other, GWT-compatible tests.
 *
 * @author Mike Bostock
 * @since 10.0
 */
@GwtCompatible // but no-op!
@NullMarked

/**
 * Service class for managing roles.
 */
public class RoleService {

    /**
     * The behavior for roles.
     */
    @Resource
    protected RoleBhv roleBhv;

    /**
     * The Fess configuration.
     */
    @Resource
    protected FessConfig fessConfig;

    /**
     * The behavior for users.
     */
    @Resource
    protected UserBhv userBhv;

    /**
     * Constructor.

        NameQueryRequest request = spy(new NameQueryRequest(mockConfig, mockName));
        byte[] dst = new byte[100];
        int dstIndex = 0;

        // Mock the superclass method to control its behavior
        doReturn(10).when((NameServicePacket) request).writeQuestionSectionWireFormat(any(byte[].class), anyInt());

        int result = request.writeBodyWireFormat(dst, dstIndex);