RequestTrace level1 = new RequestTrace("level1", root, "level1-data");
        RequestTrace level2 = new RequestTrace("level2", level1, "level2-data");
        RequestTrace level3 = new RequestTrace(level2, "level3-data");

        // Verify the chain
        assertNull(root.parent());
        assertEquals(root, level1.parent());
        assertEquals(level1, level2.parent());

        // Assert
        assertEquals(level1, queryPolicy1.level);
        assertEquals(level2, queryPolicy2.level);
        assertSame(mockPolicyHandle, queryPolicy1.handle);
        assertSame(mockPolicyHandle2, queryPolicy2.handle);
        assertSame(mockNdrObject, queryPolicy1.info);
        assertSame(mockNdrObject2, queryPolicy2.info);
    }

    @Test

     *
     * @param level the severity level of the message
     * @param message the message to be logged
     */
    default void log(@Nonnull Level level, @Nonnull String message) {
        log(level, message, null);
    }

    /**
     * Logs a message at the specified level with an associated exception.
     *
     * @param level the severity level of the message

 The Maven Team
 -----

Configuration levels in maven

 In maven configuration control happens on four differ levels: the site level, the group level,
 the project level, and the user level. On the site level you can configure maven for all users
 utilizing the local installation, the group level allows configuration management for all the projects
 that belong to the same group, the project level allows configuration management at

     * These versions correspond to different levels of validation that can be applied
     * during model building, based on the POM schema version.
     * <p>
     * The validation levels are cumulative, with higher versions including all validations
     * from lower versions plus additional checks specific to that version.
     */
    enum Version {
        /**
         * Base validation level that applies to all POM versions.

```java
HttpLoggingInterceptor logging = new HttpLoggingInterceptor();
logging.setLevel(Level.BASIC);
OkHttpClient client = new OkHttpClient.Builder()
  .addInterceptor(logging)
  .build();
```

You can change the log level at any time by calling `setLevel()`.

To log to a custom location, pass a `Logger` instance to the constructor.
```java

 * Defines common functionality for various SMB2/SMB3 file information classes used in
 * query and set file information operations, with constants for information levels.
 *
 * @author mbechler
 */
public interface FileInformation extends Decodable, Encodable {

    // information levels

    /**
     * File end-of-file information class constant.
     */
    byte FILE_ENDOFFILE_INFO = 20;

    /**

    if (configuredLoggers.add(logger)) {
      logger.useParentHandlers = false
      // log based on levels at startup to avoid logging each frame
      logger.level =
        when {
          Log.isLoggable(tag, Log.DEBUG) -> Level.FINE
          Log.isLoggable(tag, Log.INFO) -> Level.INFO
          else -> Level.WARNING
        }
      logger.addHandler(AndroidLogHandler)
    }
  }

Using the below example document:
<img width="85%" src="https://bradley.codes/static/img/jstream-levels.gif" alt="jstream"/>

we can choose to extract and act only the objects within the top-level array:
```go
f, _ := os.Open("input.json")
decoder := jstream.NewDecoder(f, 1) // extract JSON values at a depth level of 1
for mv := range decoder.Stream() {
  fmt.Printf("%v\n ", mv.Value)
}
```

output:
```

 * returning various file system information levels such as volume size and attributes.
 */
public class Trans2QueryFSInformationResponse extends SmbComTransactionResponse {

    private final int informationLevel;
    private FileSystemInformation info;

    /**
     * Constructs a Trans2QueryFSInformationResponse with the specified configuration and information level.
     *
     * @param config the SMB configuration