community can discuss and debate whether this feature is actually the *best* way to address
        the real use case, or whether or not a different abstraction might be more appropriate.


        It's okay if you can't provide complete context on a use case. We understand if you are not
        able to discuss the full details of what you're working on.

  }

  @GwtIncompatible // different overflow behavior; could probably be made to work by using ~~
  public void testConcat_overflow_negative() {
    int dim1 = 1 << 16;
    int dim2 = 1 << 15;
    assertThat(dim1 * dim2).isLessThan(0);
    testConcatOverflow(dim1, dim2);
  }

  @GwtIncompatible // different overflow behavior; could probably be made to work by using ~~

        // 1. GIVEN
        KerberosAuthData mockAuthData1 = mock(KerberosAuthData.class);
        KerberosAuthData mockAuthData2 = mock(KerberosAuthData.class);

        // Mock the parse method to return two different objects based on input
        // Must use matchers for all arguments when using any matcher
        mockedStaticAuthData.when(() -> KerberosAuthData.parse(eq(1), eq(new byte[] { 0x01 }), any(Map.class)))

        } catch (Exception e) {
            fail("Should have caught DataStoreException specifically");
        }
    }

    @Test
    public void test_multipleExceptionTypes() {
        // Test with different types of causes
        DataStoreException withIOException = new DataStoreException("IO Error", new java.io.IOException("File not found"));

    @Test
    @DisplayName("Test transaction name handling")
    void testTransactionName() {
        assertEquals("\\PIPE\\test", transaction.name, "Transaction name should be set correctly");

        // Test with different name
        transaction.name = "\\MAILSLOT\\browse";
        assertEquals("\\MAILSLOT\\browse", transaction.name, "Transaction name should be changeable");
    }

    @Test

<h2 id="introduction">Introduction</h2>

<p>
The Go memory model specifies the conditions under which
reads of a variable in one goroutine can be guaranteed to
observe values produced by writes to the same variable in a different goroutine.
</p>


<h3 id="advice">Advice</h3>

<p>
Programs that modify data being simultaneously accessed by multiple goroutines
must serialize such access.
</p>

<p>

   * Ordering.natural())}.
   *
   * @param elements the original iterable whose elements have to be permuted.
   * @return an immutable {@link Collection} containing all the different permutations of the
   *     original iterable.
   * @throws NullPointerException if the specified iterable is null or has any null elements.
   * @since 12.0
   */

            assertEquals(Integer.MAX_VALUE, SMBUtil.readInt4(buffer, 32));
            assertEquals(Integer.MAX_VALUE, SMBUtil.readInt4(buffer, 40));
        }

        @Test
        @DisplayName("Should write at different buffer positions")
        void testWriteAtDifferentPositions() {
            request.setReadLength(2048);
            request.setOffset(4096L);

            byte[] buffer = new byte[512];

    then you'll need to sign a [corporate CLA][].

You generally only need to submit a CLA once, so if you've already submitted
one (even if it was for a different project), you probably don't need to do it
again.

[individual CLA]: https://cla.developers.google.com/about/google-individual
[corporate CLA]: https://cla.developers.google.com/about/google-corporate

    for (int i = 0; i < 11; i++) {
      limiter.acquire(); // #7, showing off the warmup starting from totally cold
    }

    // make sure the areas (times) remain the same, while permits are different
    assertEvents(
        "R0.00, R1.38, R1.13, R0.88, R0.63, R0.50, R0.50, R0.50", // #1
        "U4.50", // #2
        "R0.00, R1.38, R1.13", // #3, after that the rate changes