// Execute
        final InvalidQueryException exception = new InvalidQueryException(messageCode, message, middleCause);

        // Verify cause chain is preserved
        assertEquals(middleCause, exception.getCause());
        assertEquals(rootCause, exception.getCause().getCause());
    }

    @Test
    public void test_emptyMessage() {
        // Setup

```Python
# Some Python code
```

### Triple backticks inside quadruple backticks { #triple-backticks-inside-quadruple-backticks }

Comments inside nested code block will NOT be preserved.

````
Here is a code block with quadruple backticks that contains triple backticks inside:

```python
# This is a sample Python code block
def hello_world():
    print("Hello, world!")  # Print greeting

* **Consistency with dependencies**: Gradle's ecosystem and dependencies predominantly use American English

### Exceptions

Some legitimate exceptions exist where British English or other variants must be preserved:

* **Third-party APIs and libraries**: When integrating with external APIs that use different spelling conventions

        // Verify that the cause is correctly set
        assertNotNull(runtimeException);
        assertEquals(servletException, runtimeException.getCause());

        // Verify that the message is preserved from the cause
        assertTrue(runtimeException.getMessage().contains(ServletException.class.getName()));
        assertTrue(runtimeException.getMessage().contains(errorMessage));
    }

    @Test

        String message = "Serialization test";
        UnsupportedSearchException exception = new UnsupportedSearchException(message);

        // Verify basic properties are preserved
        assertEquals(message, exception.getMessage());

        // The presence of serialVersionUID is verified at compile time
        // and the exception extends RuntimeException which is Serializable

///

The dependencies will keep working as expected, and the **best part** is that the **type information will be preserved**, which means that your editor will be able to keep providing you with **autocompletion**, **inline errors**, etc. The same for other tools like `mypy`.

        assertTrue(result instanceof BoolQueryBuilder);
        BoolQueryBuilder boolResult = (BoolQueryBuilder) result;
        assertTrue(boolResult.hasClauses());
        // Verify the original query is preserved as a must clause
        assertEquals(1, boolResult.must().size());
        assertEquals(initialQuery, boolResult.must().get(0));
    }

    // Test addSorts
    @Test
    public void test_addSorts() {

 * to a BloomFilter of M bits and k hash functions. These strategies are part of the serialized form
 * of the Bloom filters that use them, thus they must be preserved as is (no updates allowed, only
 * introduction of new versions).
 *
 * <p>Important: the order of the constants cannot change, and they cannot be deleted - we depend on
 * their ordinal for BloomFilter serialization.
 *

 *   <li><b>Model Version Handling</b>: When {@code preserve.model.version=true} is set, the consumer POM
 *       maintains the original model version (4.2.0) instead of downgrading to 4.0.0 for Maven 3 compatibility.
 *       This allows modern features like mixins to be preserved in the consumer POM.</li>
 * </ul>
 * <p>

When reviewing a pull request, it's better not to suggest changes in the same pull request, because it is LLM generated, and it won't be possible to make sure that small individual changes are replicated in other similar sections, or that they are preserved when translating the same content again.