* randomly ordered data (the probability decreases faster than exponentially in N), but if you are
 * passing in unsanitized user data then a malicious user could force it. A light shuffle of the
 * data using an unpredictable seed should normally be enough to thwart this attack.
 *
 * <p>The time taken to compute multiple quantiles on the same dataset using {@link Scale#indexes

		}
		// maximum possible length
		maxl := min(strl, xfixl)
		// compare letters
		if pre {
			// prefix, iterate left to right
			for i := range maxl {
				if xfix[i] != str[i] {
					xfix = xfix[:i]
					break
				}
			}
		} else {
			// suffix, iterate right to left
			for i := range maxl {
				xi := xfixl - i - 1
				si := strl - i - 1
				if xfix[xi] != str[si] {
					xfix = xfix[xi+1:]

        assertFalse(result);
        assertEquals(1, chain1.changePasswordCallCount);
        assertEquals(1, chain2.changePasswordCallCount);
        // allMatch may short-circuit, so chain3 might not be called
        assertTrue(chain3.changePasswordCallCount <= 1);
    }

    // Test delete with no chains
    public void test_delete_noChains() {
        User user = createTestUser("testuser");

    }

    public void test_XContentBuilderCallback_nullBuilder() {
        XContentBuilderCallback callback = (builder, params) -> {
            // Test behavior when builder operations might fail
            if (builder == null) {
                throw new IOException("Builder is null");
            }
            builder.startObject();
            builder.field("null_test", "value");

  /**
   * Prevents the given methods from being run as part of the test suite.
   *
   * <p>Note: in principle this should never need to be used, but it might be useful if the
   * semantics of an implementation disagree in unforeseen ways with the semantics expected by a
   * test, or to keep dependent builds clean in spite of an erroneous test.
   */
  @CanIgnoreReturnValue

                log.warn("Error creating SmbFile from cache for {}: {}", fileInfo.getName(), e.getMessage());
                // For testing purposes, continue processing other files
                // In a real scenario, you might want to handle this differently
            }
        }

        return files;
    }

    /**
     * Update directory cache with new listing
     *
     * @param directoryPath directory path

        // package when it is listed in the 'java.protocol.handler.pkgs' system property.
        // We use mock handlers since actual system handlers might not be available in test environment.
        System.setProperty("java.protocol.handler.pkgs", "jcifs");
        setupMockProtocolHandlers();
        URL url = new URL("http://example.com/resource");

 * </ul>
 *
 * The last point is subtle. Often the observable object will be managing its own internal state
 * using a lock, however it is dangerous to dispatch listeners while holding a lock because they
 * might run on the {@code directExecutor()} or be otherwise re-entrant (call back into your
 * object). So it is important to not call {@link #dispatch} while holding any locks. This is why

  //
  // 1. What about leaving/unlocking? Are you going to do
  //    guard.enter() paired with monitor.leave()? That might get
  //    confusing. It's nice for the finally block to look as close as
  //    possible to the thing right before the try. You could have
  //    guard.leave(), but that's a little odd as well because the
  //    guard doesn't have anything to do with leaving. You can't

            } else if (behavior == 1) { // return null
              computeNullCount.incrementAndGet();
              return null;
            } else if (behavior == 2) { // slight delay before returning
              Thread.sleep(5);
              computeCount.incrementAndGet();
              return key;
            } else {
              computeCount.incrementAndGet();