*
     * - If the stack overflowed after set()/setValue() stored its result, then a call to
     * setException() will be a no-op because the Future is already done.
     *
     * Both scenarios are bad: The output Future might never complete, or, if it does complete, it
     * might not run some of its listeners. The likely result is that the app will hang. (And of

        assertEquals((byte) 0xFF, dst[1]);
        assertEquals((byte) 0xFF, dst[2]);
        assertEquals((byte) 0xFF, dst[3]);
    }

    @Test
    @DisplayName("Test writeUTime with DST scenarios")
    void testWriteUTimeWithDST() {
        when(mockConfig.getLocalTimezone()).thenReturn(mockTimeZone);

        byte[] dst = new byte[4];
        long testTime = System.currentTimeMillis();

import jcifs.internal.smb2.Smb2Constants;
import jcifs.internal.util.SMBUtil;

/**
 * Security-focused test cases for Smb2NegotiateResponse input validation.
 * Tests various malformed input scenarios to ensure proper validation and
 * protection against buffer overflow, integer overflow, and other attacks.
 */
public class Smb2NegotiateResponseInputValidationTest {

    private Configuration mockConfig;

        assertEquals(TEST_CAPABILITIES, SMBUtil.readInt4(buffer, offset + 4)); // Capabilities
    }

    @Test
    @DisplayName("Should handle session binding scenarios")
    void testSessionBindingScenarios() throws Exception {
        // Test both true and false session binding
        boolean[] bindingValues = { true, false };

        for (boolean binding : bindingValues) {

        urlFilter.addExclude("https://example.com/.*");

        // Exclude should take precedence
        assertFalse(urlFilter.match("https://example.com/page"));
    }

    /**
     * Test URL normalization scenarios
     */
    public void test_urlNormalization() {
        String sessionId = "test-session-026";
        urlFilter.init(sessionId);

        urlFilter.addInclude("https://example.com/path/.*");

        }

        public void resetCounters() {
            matchCallCount = 0;
            lastResponseData = null;
        }
    }

    /**
     * Another concrete implementation for testing different scenarios
     */
    public static class ConditionalAbstractRule extends AbstractRule {
        private static final long serialVersionUID = 1L;

        private String urlPattern;
        private String mimeTypePattern;

            // Then
            verify(transportPool).removeTransport(transport);
            verify(transportPool).removeTransport(transport2);
        }
    }

    @Nested
    @DisplayName("Integration Scenarios")
    class IntegrationTests {

        @Test
        @DisplayName("Should complete full connection lifecycle")
        void testFullConnectionLifecycle() throws Exception {
            // Given

 *
 * <p>The job supports selective crawling by specifying configuration IDs for different
 * types of crawlers (web, file, data). It manages the crawler process lifecycle,
 * handles timeout scenarios, and ensures proper cleanup of resources.</p>
 *
 * <p>Key features:</p>
 * <ul>
 *   <li>Concurrent crawler process management with configurable limits</li>
 *   <li>Selective crawling based on configuration IDs</li>

**Configuration**: Set `web.api.gsa=true` in `system.properties` to enable GSA compatibility features.

For most migration scenarios, we recommend using the modern JSON Search API (`/api/v1/documents`) instead.

### Admin APIs

All admin APIs require authentication (`-u admin:admin` or Bearer token).

**Base Path**: `/api/admin/`

- The scheduling queue didn't notice any extenders' failures, it could miss some cluster events,
  and it could end up Pods rejected by Extenders stuck in unschedulable pod pool in 5min in the worst-case scenario.
  Now, the scheduling queue notices extenders' failures and requeue Pods rejected by Extenders appropriately. ([#122043](https://github.com/kubernetes/kubernetes/pull/122043), [@sanposhiho](https://github.com/sanposhiho)) [SIG Scheduling]