final Throwable[] causes = mcae.getCauses();
                if (causes.length > 0) {
                    t = causes[causes.length - 1];
                }
            }

            String errorName;
            final Throwable cause = t.getCause();
            if (cause != null) {
                errorName = cause.getClass().getCanonicalName();
            } else {

    }

    @Test
    public void test_constructor_withCause() {
        // Test with cause only
        Exception cause = new IllegalStateException("Underlying error");
        DataStoreException exception = new DataStoreException(cause);

        assertNotNull(exception);
        assertEquals(cause, exception.getCause());
        assertEquals("java.lang.IllegalStateException: Underlying error", exception.getMessage());

        // Test constructor with null message but valid cause
        Exception cause = new IllegalArgumentException("Invalid argument");
        DictionaryException exception = new DictionaryException(null, cause);

        assertNotNull(exception);
        assertNull(exception.getMessage());
        assertNotNull(exception.getCause());
        assertEquals(cause, exception.getCause());
    }

    @Test

  * For polynull public APIs, the solution has to be decided on a case-by-case basis.

Do not remove `null` checks on public API boundaries, even if the annotations (or rather lack of them) suggest this.
Not all client code is compiled with NullAway.
Do not make a parameter `@Nullable` just to check and throw a `NullPointerException` when it is `null`. 

## Consequences

* Classes are forced to have consistent nullability annotations.

            executionOrder.clear();
        }
    }

    // Test class that causes NullPointerException
    private static class NullPointerScoreBooster extends ScoreBooster {
        @Override
        public long process() {
            // This will cause NullPointerException when auto-unboxing
            Long nullValue = null;
            return nullValue;
        }
    }

        // Test constructor with message and cause
        String message = "Storage operation failed";
        Exception cause = new RuntimeException("Underlying error");
        StorageException exception = new StorageException(message, cause);

        assertNotNull(exception);
        assertEquals(message, exception.getMessage());
        assertEquals(cause, exception.getCause());
    }

    @Test

REM FESS_JAVA_OPTS=%FESS_JAVA_OPTS% -Djavax.net.ssl.trustStore=/tech/elastic/config/truststore.jks
REM FESS_JAVA_OPTS=%FESS_JAVA_OPTS% -Djavax.net.ssl.trustStorePassword=changeit

REM Causes the JVM to dump its heap on OutOfMemory.
REM set FESS_JAVA_OPTS=%FESS_JAVA_OPTS% -XX:+HeapDumpOnOutOfMemoryError
REM The path to the heap dump location, note directory must exists and have enough
REM space for a full heap dump.

FESS_JAVA_OPTS="$FESS_JAVA_OPTS -Dlog4j2.disable.jmx=true"
FESS_JAVA_OPTS="$FESS_JAVA_OPTS -Dlog4j2.formatMsgNoLookups=true"
FESS_JAVA_OPTS="$FESS_JAVA_OPTS -Dlog4j.skipJansi=true"

# Causes the JVM to dump its heap on OutOfMemory.
#FESS_JAVA_OPTS="$FESS_JAVA_OPTS -XX:+HeapDumpOnOutOfMemoryError"
# The path to the heap dump location, note directory must exists and have enough
# space for a full heap dump.

        applyRule<DependencyAdditionRule>("com.google.apis:google-api-services-storage", "org.slf4j:jcl-over-slf4j")

        // asciidoctorj depends on a lot of stuff, which causes `Can't create process, argument list too long` on Windows
        applyRule<DependencyRemovalByNameRule>("org.gradle:sample-discovery", setOf("asciidoctorj", "asciidoctorj-api"))

        withModule<RemoveXmlApisRule>("jaxen:jaxen")

        // Test constructor with message and cause
        String message = "Command execution failed with error";
        Throwable cause = new IllegalStateException("Invalid state");
        CommandExecutionException exception = new CommandExecutionException(message, cause);

        assertNotNull(exception);
        assertEquals(message, exception.getMessage());
        assertEquals(cause, exception.getCause());