+ " Your JAR contains rogue Maven Plugin metadata."
                                                + " Possible causes may be: shaded into this JAR some Maven Plugin or some rogue resource.",
                                        artifact.getGroupId(),
                                        artifact.getArtifactId(),

                    return (int) misses.incrementAndGet();
                  }
                });

    // To start, fill up the cache.
    // Each miss both increments the counter and causes the map to grow by one,
    // so until evictions begin, the size of the map is the greatest return
    // value seen so far
    while (cache.getUnchecked(nextRandomKey()) < maximumSize) {}

    requests.set(0);

        // Ensure jcl-over-slf4j is pulled in when we use GCS so it can conflict.
        applyRule<DependencyAdditionRule>(libs.gcs, libs.jclToSlf4j)

        // 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")

        assertEquals(rootCause, withCauseException.getRootCause());
        assertEquals(withCauseException.getCause(), withCauseException.getRootCause());

        // Test with nested causes
        RuntimeException middleCause = new RuntimeException("Middle", rootCause);
        TransportException nestedCauseException = new TransportException("Nested", middleCause);

        }
    }

    @Override
    public void omitForCycle(Artifact omitted) {
        logger.debug(indent + omitted + " (removed - causes a cycle in the graph)");
    }

    @Override
    public void updateScopeCurrentPom(Artifact artifact, String ignoredScope) {

We utilize nullness annotations in Java code and somewhat rely on IDE warnings to guide us.
However, the Java code we have is not fully annotated, which causes several consequences:
* IDE warnings can be misleading
* Redundant null checks may increase binary size, hurt performance, and increase cognitive load for readers
* Missing null checks may cause NullPointerException

                "System.arraycopy should throw for insufficient destination space");
    }

    @Test
    @DisplayName("encode() throws when dstIndex causes overflow")
    void encodeThrowsWhenDstIndexCausesOverflow() {
        byte[] src = makeSeq(5);
        Encodable enc = new ByteEncodable(src, 0, 5);

     */
    @Test
    void testGetMessageByDcerpcError_largerThanAny() {
        int unknownCode = 0x7FFFFFFF; // Max int value

        // The current implementation has a bug in the binary search that causes ArrayIndexOutOfBoundsException
        assertThrows(ArrayIndexOutOfBoundsException.class, () -> {
            DcerpcException.getMessageByDcerpcError(unknownCode);

    }

    @Test
    void testConcurrentWeightCalculation() throws Exception {
        // Test that concurrent weight calculation doesn't cause recursive update issues
        // This test simulates the scenario that causes the IllegalStateException

        int numThreads = 10;
        int numIterations = 100;
        ExecutorService executor = Executors.newFixedThreadPool(numThreads);

            expected = NtStatus.NT_STATUS_UNSUCCESSFUL;
        }
        assertEquals(expected, ex.getNtStatus(), "Status should match mapping or fallback");
    }

    /**
     * Verify that root causes are stored and returned correctly.
     */
    @Test
    @DisplayName("Root cause propagation")
    void testRootCausePropagation() {
        Throwable root = mock(Throwable.class);