// Act & Assert: attempting to call any method on null should throw NPE
        Assertions.assertThrows(NullPointerException.class, () -> {
            // Intentionally dereference null to validate exception behavior
            // This checks that callers must handle null references defensively
            info.getSize();
        });
    }

                || FAIL_NEVER.equals(failureBehavior)) {
            this.failureBehavior = failureBehavior;
        } else {
            throw new IllegalArgumentException("Invalid failure behavior (must be one of: '" + FAIL_FAST + "', '"
                    + FAIL_AT_END + "', '" + FAIL_NEVER + "').");
        }
    }

    public String getFailureBehavior() {
        return failureBehavior;
    }

    /**
     * Adds the given source to the given project.
     * If a source already exists for the given scope, language and directory,
     * then the behavior depends on the {@code ProjectManager} implementation.
     * It may do nothing or thrown {@linkplain IllegalArgumentException}.
     *
     * @param project the project to update
     * @param source the source to add

versioning with [object lifecycle management](https://github.com/minio/minio/blob/master/docs/bucket/lifecycle/README.md).  If you have an object expiration lifecycle policy in your non-versioned bucket and you want to maintain the same permanent delete behavior when on versioning-enabled bucket, you must add a noncurrent expiration policy. The noncurrent expiration lifecycle policy will manage the deletes of the noncurrent object versions in the versioning-enabled bucket. (A version-enabled bucket maintains...

        assertEquals(0, config.getBatchLimit("TreeConnectAndX.QueryInformation"));

        // Test unspecified batch limit
        assertEquals(1, config.getBatchLimit("UnknownCommand"));

        // Test caching behavior
        assertEquals(0, config.getBatchLimit("TreeConnectAndX.QueryInformation"));
    }

    @Test
    @DisplayName("Test getBatchLimit with custom implementation")

    private static final String TEST_SERVER = "server";
    private static final String TEST_ENDPOINT = "\\pipe\\test";

    @BeforeEach
    void setUp() throws IOException {
        // Setup mock behavior with lenient stubbing to avoid UnnecessaryStubbingException
        lenient().when(mockSmbNamedPipe.openPipe()).thenReturn(mockSmbPipeHandle);

        // Act
        long value = (long) f.get(null);

        // Assert
        assertEquals(2283323396289696982L, value, "serialVersionUID should be stable");
    }

    // Behavior check: toString contains class name and message when present
    @Test
    @DisplayName("toString contains class name and message when provided")
    void toString_containsClassName_and_Message() {
        // Arrange

import org.jspecify.annotations.Nullable;

/**
 * An executor service which forwards all its method calls to another executor service. Subclasses
 * should override one or more methods to modify the behavior of the backing executor service as
 * desired per the <a href="http://en.wikipedia.org/wiki/Decorator_pattern">decorator pattern</a>.
 *
 * <p><b>{@code default} method warning:</b> This class does <i>not</i> forward calls to {@code

            // Apply dependency inference
            UpgradeContext context = createMockContext();
            strategy.doApply(context, pomMap);

            // Verify correct behavior when version doesn't match:
            // - groupId should be removed (can be inferred from project regardless of version)
            // - version should remain (doesn't match project version, so can't be inferred)

   * whether nulls were to be permitted or forbidden, but presumably the eventual fix will be to
   * permit them, as it seems more likely that code would depend on that behavior than on the other.
   * Thus, we say the bug is in add(), which fails to support null.
   */
  @J2ktIncompatible
  @GwtIncompatible // reflection
  public static Method getAddNullSupportedMethod() {