} unicode_string;

	/* 
	 * typedef struct _SID_IDENTIFIER_AUTHORITY {
	 *     UCHAR Value[6];
	 * } SID_IDENTIFIER_AUTHORITY, *PSID_IDENTIFIER_AUTHORITY;
	 * 
	 * #define SECURITY_NT_AUTHORITY           {0,0,0,0,0,5}
	 * 
	 * typedef struct _SID {
	 *    UCHAR Revision;
	 *    UCHAR SubAuthorityCount;
	 *    SID_IDENTIFIER_AUTHORITY IdentifierAuthority;

	} unicode_string;

	/* 
	 * typedef struct _SID_IDENTIFIER_AUTHORITY {
	 *     UCHAR Value[6];
	 * } SID_IDENTIFIER_AUTHORITY, *PSID_IDENTIFIER_AUTHORITY;
	 * 
	 * #define SECURITY_NT_AUTHORITY           {0,0,0,0,0,5}
	 * 
	 * typedef struct _SID {
	 *    UCHAR Revision;
	 *    UCHAR SubAuthorityCount;
	 *    SID_IDENTIFIER_AUTHORITY IdentifierAuthority;

# Background Tasks { #background-tasks }

You can define background tasks to be run *after* returning a response.

This is useful for operations that need to happen after a request, but that the client doesn't really have to be waiting for the operation to complete before receiving the response.

This includes, for example:

* Email notifications sent after performing an action:

    } else {
      assertThrows(UnsupportedOperationException.class, map::clear);
    }
    assertInvariants(map);
  }

  @J2ktIncompatible // https://youtrack.jetbrains.com/issue/KT-58242/ undefined behavior (crash)
  public void testContainsKey() {
    Map<K, V> map;
    K unmappedKey;
    try {
      map = makePopulatedMap();
      unmappedKey = getKeyNotInPopulatedMap();

# Security Tools

When you need to declare dependencies with OAuth2 scopes you use `Security()`.

But you still need to define what is the dependable, the callable that you pass as a parameter to `Depends()` or `Security()`.

There are multiple tools that you can use to create those dependables, and they get integrated into OpenAPI so they are shown in the automatic docs UI, they can be used by automatically generated clients and SDKs, etc.

 * KIND, either express or implied.  See the License for the
 * specific language governing permissions and limitations
 * under the License.
 */

/**
 * Provides classes for Maven plugin descriptors that define plugin metadata, configuration,
 * and execution parameters. These descriptors are typically stored in plugin.xml files
 * within the META-INF/maven directory of plugin JARs.
 *
 * @since 4.0.0
 */

        const containerStyle = getComputedStyle(this.container);
        this.container.style.width = containerStyle.width !== '0px' ?
            containerStyle.width : undefined;
        this.container.style.minHeight = containerStyle.height !== '0px' ?
            containerStyle.height : undefined;

        this.container.setAttribute('data-termynal', '');
        this.container.innerHTML = '';
        for (let line of this.lines) {

 * <ul>
 *   <li><b>Warning:</b> as with any collection, it is almost always a bad idea to modify an element
 *       (in a way that affects its {@link Object#equals} behavior) while it is contained in a
 *       collection. Undefined behavior and bugs will result. It's generally best to avoid using
 *       mutable objects as elements at all, as many users may expect your "immutable" object to be
 *       <i>deeply</i> immutable.
 * </ul>
 *

# `UploadFile` class

You can define *path operation function* parameters to be of the type `UploadFile` to receive files from the request.

You can import it directly from `fastapi`:

```python
from fastapi import UploadFile
```

::: fastapi.UploadFile
    options:
        members:
            - file
            - filename
            - size
            - headers
            - content_type
            - read

* response data injection systems
* etc.

## Simple and Powerful { #simple-and-powerful }

Although the hierarchical dependency injection system is very simple to define and use, it's still very powerful.

You can define dependencies that in turn can define dependencies themselves.