assertNotNull(results);
            // Should return empty or minimal results
            assertTrue(results.size() <= 10);
        }
    }

    /**
     * Test search with negative start position (should be handled gracefully).
     */
    @Test
    public void test_searchWithNegativeStartPosition() throws Exception {

        }

        when(mockConfig.getLmHostsFileName()).thenReturn(lmhostsFile.getAbsolutePath());

        // First call should read the file
        NbtAddress result1 = lmhosts.getByName("TESTHOST", mockContext);
        assertNotNull(result1);

        // Second call should use cached data (file not modified)
        NbtAddress result2 = lmhosts.getByName("TESTHOST", mockContext);
        assertNotNull(result2);

Given these constraints, we cannot always follow best practices.  This ADR proposes the way we should handle the use of Provider APIs in the gradle/gradle codebase.

## Decision

### Types of properties that should not use lazy types

The guidelines below do not apply to all properties. There are cases where the lazy types should not be used:

#### Non-calculated values

These are inappropriate uses of lazy types:

	// SS parity drives should be greater than or equal to minParityDrives.
	// Parity below minParityDrives is not supported.
	if ssParity > 0 && ssParity < minParityDrives {
		return fmt.Errorf("parity %d should be greater than or equal to %d",
			ssParity, minParityDrives)
	}

	if ssParity > setDriveCount/2 {
		return fmt.Errorf("parity %d should be less than or equal to %d", ssParity, setDriveCount/2)
	}

    }

    /**
     * Test isSortField with empty array - should return false, not throw exception.
     * This test addresses the Copilot AI concern about empty arrays.
     */
    @Test
    public void test_isSortField_withEmptyArray_returnsFalse() {
        String[] emptyFields = {};
        queryFieldConfig.setSortFields(emptyFields);

        // Set should be empty but not null

            thread.join();
        }

        // All threads should observe alive=false due to volatile
        for (int i = 0; i < 10; i++) {
            assertFalse("Thread " + i + " should see alive=false", observedValues[i]);
        }
    }

    /**
     * Test concurrent access to stop() method.
     * Multiple threads call stop() simultaneously - should be safe.
     */
    @Test

            processor.setSearcher(new TestSearcher(100));
            processor.register(new ExceptionThrowingSearcher(new RuntimeException("Test exception")));
            processor.init();

            // Should handle exception gracefully and return results from working searcher
            final List<Map<String, Object>> results = processor.search("*", new TestSearchRequestParams(0, 10, 0), OptionalThing.empty());

    assertTrue("containsValue(present) should return true", getMap().containsValue(v0()));
  }

  public void testContains_no() {
    assertFalse("containsValue(notPresent) should return false", getMap().containsValue(v3()));
  }

  @MapFeature.Require(ALLOWS_NULL_VALUE_QUERIES)
  public void testContains_nullNotContainedButAllowed() {
    assertFalse("containsValue(null) should return false", getMap().containsValue(null));
  }

            caughtSpecific = true;
        } catch (RuntimeException e) {
            caughtRuntime = true;
        }

        assertTrue("Should have caught DictionaryExpiredException", caughtSpecific);
        assertFalse("Should not have caught as RuntimeException", caughtRuntime);
    }

    @Test
    public void test_rethrow() {
        // Test rethrowing the exception

   * should use this method over {@link #setCountCheckReturnValue(Object, int)} when they expect
   * {@code setCount()} to throw an exception, as checking the return value could produce an
   * incorrect error message like "setCount() should return the original count" instead of the
   * message passed to a later invocation of {@code fail()}, like "setCount should throw
   * UnsupportedOperationException."
   */