// There are several well-known algorithms for rotating part of an array (or, equivalently,
    // exchanging two blocks of memory). This classic text by Gries and Mills mentions several:
    // https://ecommons.cornell.edu/bitstream/handle/1813/6292/81-452.pdf.
    // (1) "Reversal", the one we have here.
    // (2) "Dolphin". If we're rotating an array a of size n by a distance of d, then element a[0]

- kubeadm: Use generic terminology in logs instead of direct mentions of YAML/JSON  ([#130345](https://github.com/kubernetes/kubernetes/pull/130345), [@HirazawaUi](https://github.com/HirazawaUi))
- kubeadm: removed preflight check for `ip`, `iptables`, `ethtool` and `tc` on Linux nodes. 

            assertFalse("Exception message should not be empty", message.trim().isEmpty());
            assertTrue("Exception message should mention 'inputstream'", message.toLowerCase().contains("inputstream"));
            assertTrue("Exception message should mention 'null'", message.toLowerCase().contains("null"));
        }
    }

    /**
     * Test that validateInputStream does not modify or consume the stream.

        try {
            zipExtractor.getText(invalidStream, null);
            fail("Expected ExtractException");
        } catch (final ExtractException e) {
            assertTrue("Error message should mention ZIP archive", e.getMessage().contains("ZIP archive"));
            assertTrue("Error message should indicate failure",

    return FluentIterable.from(ImmutableList.<Number>of());
  }

  /*
   * The following tests demonstrate the shortcomings of or() and test that the casting workaround
   * mentioned in the method Javadoc does in fact compile.
   */

  @SuppressWarnings("unused") // compilation test
  public void testSampleCodeError1() {
    Optional<Integer> optionalInt = getSomeOptionalInt();

        try {
            FileUtil.readBytes(largeFile);
            fail("Expected IORuntimeException for large file");
        } catch (final IORuntimeException e) {
            assertTrue("Error message should mention file size", e.getMessage().contains("File too large"));
        }
    }

    /**
     * Test readBytes with file within size limit
     *
     * @throws Exception
     */
    @Test

        }

        return bestDelimiter;
    }

    /**
     * Counts occurrences of a character in a string, excluding quoted sections.
     *
     * @param line the line to analyze
     * @param ch the character to count
     * @return the number of occurrences
     */
    protected int countOccurrences(final String line, final char ch) {

            // It could be either "Unexpected number of update indices" or "Unexpected number of search indices"
            // depending on which check fails first
            assertTrue("Exception message should mention unexpected indices: " + exceptionMessage,
                    exceptionMessage.contains("Unexpected number of update indices")
                            || exceptionMessage.contains("Unexpected number of search indices"));

start by opening a new issue describing the bug or feature you're intending to
fix. Even if you think it's relatively minor, it's helpful to know what people
are working on. And as mentioned above, API changes should be discussed
thoroughly before moving to code.

Some examples of types of pull requests that are immediately helpful:

  - Fixing a bug without changing a public API.

### Core Principles

**Thread Safety**:
- `AtomicLong` for counters (`CrawlerContext.accessCount`)
- `volatile` for status flags
- Synchronized blocks for critical sections
- Thread-local storage via `CrawlingParameterUtil`

**Resource Management**:
- `AutoCloseable` throughout
- `DeferredFileOutputStream` for large responses (temp files for >1MB)
- Connection pooling with limits