// says its local for a given host - it is true for all endpoints
	// for the same host. Following code ensures that this assumption
	// is true and it works in all scenarios and it is safe to assume
	// for a given host.
	endpointLocalMap := make(map[string]bool)
	for _, ep := range endpoints {
		if ep.IsLocal {
			endpointLocalMap[ep.Host] = ep.IsLocal
		}
	}

        }

        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

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

 *
 * <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>

- 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]

	// for this instance of unlocker, we should let the
	// caller know that lock is not successfully released
	// yet.
	if len(locks)-tolerance == tolerance {
		// In case of split brain scenarios where
		// tolerance is exactly half of the len(*locks)
		// then we need to make sure we have unlocked
		// upto tolerance+1 - especially for RUnlock
		// to ensure that we don't end up with active

 * using the Apache Tika library. It extends {@link PasswordBasedExtractor} to handle password-protected files.
 * </p>
 *
 * <p>
 * This class provides methods to extract text from an input stream, handling different scenarios such as:
 * </p>
 * <ul>
 *   <li>Normalizing text content</li>
 *   <li>Handling resource names and content types</li>
 *   <li>Retrying extraction without resource name or content type if the initial attempt fails</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/`

            </project>
            """;

        Document doc = Document.of(pomXml);
        Element root = doc.root();

        // Insert elements with various text content scenarios
        DomUtils.insertContentElement(root, "name", "Test Project Name");
        DomUtils.insertContentElement(root, "description", ""); // Empty content
        DomUtils.insertContentElement(root, "url", null); // Null content