if (isBom) {
                return buildBomWithoutFlatten(session, project, src);
            } else {
                return buildPom(session, project, src);
            }
        }
        // Default behavior: flatten the consumer POM
        if (POM_PACKAGING.equals(packaging)) {
            if (isBom) {
                return buildBom(session, project, src);
            } else {

        assertEquals(16, serverData.guid.length);
    }

    /**
     * Test that modifying the original array affects the field (reference test)
     */
    @Test
    @DisplayName("Test byte array reference behavior")
    public void testByteArrayReference() {
        // Given
        byte[] originalKey = new byte[] { 0x01, 0x02, 0x03, 0x04 };
        serverData.encryptionKey = originalKey;

            long skipped = sis.skip(10);
            // If it doesn't throw, it should only skip what's available
            assertEquals(3, skipped);
        } catch (IOException e) {
            // This is also acceptable behavior - skip may fail when it runs out of data
            assertTrue(e.getMessage().contains("unexpected EOF"));
        }
    }

    @Test
    @DisplayName("Keep-alive packets are transparently skipped")

    private int crc2 = 0;
    private int crc3 = 0;

    @Override
    protected void process(ByteBuffer bb) {
      if (finished) {
        throw new IllegalStateException(
            "The behavior of calling any method after calling hash() is undefined.");
      }
      while (bb.remaining() >= 16) {
        crc0 = computeForWord(crc0);
        crc1 = computeForWord(crc1);
        crc2 = computeForWord(crc2);

   a given time.

=== Bad practices

==== Use randomized-testing for coverage

In general, randomization should be used for parameters that are not expected
to affect the behavior of the functionality that is being tested. For instance
the number of shards should not impact `date_histogram` aggregations, and the
choice of the `store` type (`niofs` vs `mmapfs`) does not affect the results of

   * reclaimed.
   *
   * If any of this fails along the way, we fall back to loading Finalizer directly in the
   * application class loader.
   *
   * NOTE: The tests for this behavior (FinalizableReferenceQueueClassLoaderUnloadingTest) fail
   * strangely when run in JDK 9. We are considering this a known issue. Please see
   * https://github.com/google/guava/issues/3086 for more information.
   */

    if (o == null) {
      return "null";
    }
    try {
      return o.toString();
    } catch (Exception e) { // sneaky checked exception
      // Default toString() behavior - see Object.toString()
      String objectToString =
          o.getClass().getName() + '@' + Integer.toHexString(System.identityHashCode(o));

   * implemented in terms of that method (though they will likely be overridden by subclasses for
   * performance reasons).) This means that a call to this method have can different behavior in GWT
   * and non-GWT environments UNLESS subclasses are careful to always override all methods
   * implemented in terms of sortedDelegate (except comparator()).
   */

        // Create the transport with safe defaults (no real sockets)
        transport = new SmbTransportImpl(ctx, address, 445, null, 0, false);

        // Reset MID to a known starting point for deterministic behavior
        setField(transport, "mid", new AtomicLong());
    }

    // Utility: reflectively set a private/protected field (searches up the hierarchy)
    private static void setField(Object target, String name, Object value) {

)

// Reject new lock requests immediately when this many are queued
// for the local lock mutex.
// We do not block unlocking or maintenance, but they add to the count.
// The limit is set to allow for bursty behavior,
// but prevent requests to overload the server completely.
// Rejected clients are expected to retry.
const lockMutexWaitLimit = 1000