* have the same nullness as E." Since we can't, we declare it to return nullable elements, and
     * we can override it in our non-null-guaranteeing subtypes to present a better signature to
     * their users.
     *
     * However, the checker *we* use has this special knowledge about `Collection.toArray()` anyway,
     * so in our implementation code, we can rely on that. That's why the expression below

    }

    public void test_stackTracePopulated() {
        // Test that stack trace is properly populated
        InvalidAccessTokenException exception = new InvalidAccessTokenException("JWT", "Invalid signature");

        StackTraceElement[] stackTrace = exception.getStackTrace();
        assertTrue(stackTrace.length > 0);

        // First element should be from this test method

    assertThat(min(2, 1, reverse)).isEqualTo(2);
    assertThat(max(1, 2, reverse)).isEqualTo(1);
    assertThat(max(2, 1, reverse)).isEqualTo(1);
  }

  /**
   * Fails compilation if the signature of min and max is changed to take {@code Comparator<T>}
   * instead of {@code Comparator<? super T>}.
   */
  public void testMinMaxWithSupertypeComparator() {

    while (!descendant.equals(ancestor)) {
      classes.add(descendant);
      descendant = descendant.getSuperclass();
    }

    return classes;
  }

  /**
   * Not really a signature -- just the parts that affect whether one method is a fauxveride of a
   * method from an ancestor class.
   *
   * <p>See JLS 8.4.2 for the definition of the related "override-equivalent."
   */

        }
    }

    @Nested
    @DisplayName("Resource Unwrapping Tests")
    class ResourceUnwrappingTest {

        @Test
        @DisplayName("Should provide unwrap method with correct signature")
        void shouldProvideUnwrapMethod() {
            assertDoesNotThrow(() -> {
                java.lang.reflect.Method unwrapMethod = SmbSession.class.getMethod("unwrap", Class.class);

                }
            }

            /* Verification fails (w/ W2K3 server at least) if status is not 0. This
             * suggests MS doesn't compute the signature (correctly) for error responses
             * (perhaps for DOS reasons).
             */
            if (digest != null && resp.errorCode == 0) {
                digest.verify(BUF, 4, resp);
            }

            throw new CIFSException("Signing is not initialized");
        }

        final int ver = SMBUtil.readInt4(mic, 0);
        if (ver != 1) {
            throw new SmbUnsupportedOperationException("Invalid signature version");
        }

        final MessageDigest mac = Crypto.getHMACT64(sk);
        final int seq = SMBUtil.readInt4(mic, 12);
        mac.update(mic, 12, 4); // sequence

            <signature>
              <groupId>com.toasttab.android</groupId>
              <artifactId>gummy-bears-api-23</artifactId>
              <version>0.12.0</version>
              <!-- TODO(cpovirk): In principle, it would make sense to *also* test compatibility with JDK 1.8, since guava-android also has JRE users. -->
            </signature>
            <ignores>

        // Reserved/Async ID
        SMBUtil.writeInt8(0, buffer, bufferIndex + 32);
        // Session ID
        SMBUtil.writeInt8(0, buffer, bufferIndex + 40);
        // Signature
        System.arraycopy(new byte[16], 0, buffer, bufferIndex + 48, 16);

        // Body starts at bufferIndex + 64
        // Structure size = 2
        SMBUtil.writeInt2(2, buffer, bufferIndex + 64);

 * {@code enterXxx}, {@code tryEnterXxx}, and {@code waitForXxx} method of the {@code Monitor} class
 * is analyzed reflectively to determine appropriate test cases based on its signature. Additional
 * ad hoc test cases can be found in {@link SupplementalMonitorTest}.
 *
 * @author Justin T. Sampson
 */
@NullUnmarked
public class GeneratedMonitorTest extends TestCase {