}

    public void test_stackTraceForMessageAndCauseConstructor() {
        // Test that stack trace is available when using message and cause constructor
        ThumbnailGenerationException exception = new ThumbnailGenerationException("Test", new Exception());

        // The message and cause constructor uses normal super call, so stack trace should be available
        assertTrue(exception.getStackTrace().length > 0);
    }

 *       suffice because we our Android users and tests are using the open-source version, which
 *       would no longer have the problematic test. But why bother when we can instead strip it with
 *       a more precisely named annotation?
 *   <li>While a dependency on Android ought to be easy if it's for annotations only, it will
 *       probably require adding the dep to various ACLs, license files, and Proguard

import org.mockito.Mockito;
import org.mockito.junit.jupiter.MockitoExtension;

/**
 * Tests for SmbBasicFileInfo interface.
 * The tests exercise typical, edge, and null scenarios using a simple
 * implementation and a Mockito mock to verify interactions.
 */
@ExtendWith(MockitoExtension.class)
public class SmbBasicFileInfoTest {

    /**
     * Simple concrete implementation used for testing return values.

    id: generics-proposal
    attributes:
      label: Is this about generics?
      description: If so, how does this relate to the accepted design and other generics proposals?
      placeholder: |
       Yes or No

       If yes, 
        1. how does this relate to the accepted design and other generics proposals?

    validations:
      required: true

  - type: textarea
    id: proposal
    attributes:

For example, with an ID of `42`, this would render:

```html
<a href="/items/42">
```

## Templates and static files { #templates-and-static-files }

You can also use `url_for()` inside of the template, and use it, for example, with the `StaticFiles` you mounted with the `name="static"`.

```jinja hl_lines="4"
{!../../docs_src/templates/templates/item.html!}
```

- Creation and deletion of buckets and objects
- Creation and deletion of all IAM users, groups, policies and their mappings to users or groups
- Creation of STS credentials
- Creation and deletion of service accounts (except those owned by the root user)
- Changes to Bucket features such as:
  - Bucket Policies
  - Bucket Tags

### Certificate Directory

   * same structural relationships as those in this network.
   *
   * <p>Thus, two networks A and B are equal if <b>all</b> of the following are true:
   *
   * <ul>
   *   <li>A and B have equal {@link #isDirected() directedness}.
   *   <li>A and B have equal {@link #nodes() node sets}.
   *   <li>A and B have equal {@link #edges() edge sets}.

- Fixes a 1.29.0 regression that introduced a possible data race that could cause panics in kube-controller-manager and kube-scheduler ([#124518](https://github.com/kubernetes/kubernetes/pull/124518), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery and Scheduling]

     * Default constructor for DocList.
     * Creates a new empty document list with zero content size and processing time.
     */
    public DocList() {
        super();
    }

    /**
     * Clears all documents from the list and resets metrics.
     * Removes all documents and resets content size and processing time to zero.
     */
    @Override
    public void clear() {
        super.clear();
        contentSize = 0;