// Different instances
        assertFalse(CrawlerStatus.INITIALIZING.equals(CrawlerStatus.RUNNING));
        assertFalse(CrawlerStatus.INITIALIZING.equals(CrawlerStatus.DONE));
        assertFalse(CrawlerStatus.RUNNING.equals(CrawlerStatus.DONE));

        // Null comparison
        assertFalse(CrawlerStatus.INITIALIZING.equals(null));

        // Different type comparison

        assertEquals(1, component.getId());

        TestComponent component2 = factory.create();
        assertNotNull(component2);
        assertEquals(2, component2.getId());

        // Different instances for prototype
        assertNotSame(component, component2);
    }

    /**
     * Test creation with null component name
     */
    public void test_create_nullComponentName() {

     */
    public void test_processUrl_basic() {
        String sessionId = "test-session-012";
        urlFilter.init(sessionId);

        // Process URL should handle different URL formats
        urlFilter.processUrl("https://example.com/");
        urlFilter.processUrl("http://test.com/path/to/page");
        urlFilter.processUrl("ftp://files.server.com/documents/");

         * 2b. If the resolved types are different from the original types, things are trickier. The
         * only way to get a TypeVariable instance for the resolved types is to create our own. The
         * created TypeVariable will not interoperate with any JDK TypeVariable. But this is OK: We
         * don't _want_ our new TypeVariable to be equal to the JDK TypeVariable because it has

      # When we specify multiple JDKs, the final one becomes the default, which is used to execute Maven itself.
      # Our Maven configuration then specifies different JDKs to use for some of the steps:
      # - 11 (sometimes) to *download* to support anyone who runs JDiff or our Gradle integration tests (including our doc snapshots and our Java 11 CI test run) but not to use directly

        TestAbstractRule testRule = new TestAbstractRule();

        ResponseData responseData = new ResponseData();
        responseData.setUrl("http://example.com");

        // Different implementations should behave differently
        conditionalRule.setUrlPattern("https://.*");
        assertFalse(conditionalRule.match(responseData)); // Doesn't match pattern

        testRule.setMatchResult(true);

            lastResponseData = null;
            returnedResultData = null;
            throwException = false;
        }
    }

    /**
     * Another concrete implementation for testing different scenarios
     */
    public static class NameTrackingTransformer extends AbstractTransformer {
        private final List<String> nameHistory = new ArrayList<>();

        @Override

        assertSame(sharedProcessor, rule3.getResponseProcessor());

        // Different rule IDs
        assertEquals("rule1", rule1.getRuleId());
        assertEquals("rule2", rule2.getRuleId());
        assertEquals("rule3", rule3.getRuleId());

        // Different match results
        ResponseData responseData = new ResponseData();
        assertTrue(rule1.match(responseData));

         * 2b. If the resolved types are different from the original types, things are trickier. The
         * only way to get a TypeVariable instance for the resolved types is to create our own. The
         * created TypeVariable will not interoperate with any JDK TypeVariable. But this is OK: We
         * don't _want_ our new TypeVariable to be equal to the JDK TypeVariable because it has

	if objectAPI == nil {
		return
	}

	// Proxy rebalance-status to first pool first node, so that users see a
	// consistent view of rebalance progress even though different rebalancing
	// pools may temporarily have out of date info on the others.
	if ep := globalEndpoints[0].Endpoints[0]; !ep.IsLocal {
		for nodeIdx, proxyEp := range globalProxyEndpoints {
			if proxyEp.Host == ep.Host {