import org.jspecify.annotations.Nullable;

/**
 * To be implemented by test generators that can produce test subjects without requiring any
 * parameters.
 *
 * @param <T> the type created by this generator.
 * @author George van den Driessche
 */
@GwtCompatible
@NullMarked
public interface TestSubjectGenerator<T extends @Nullable Object> {
  T createTestSubject();

### Other utility functions { #other-utility-functions }

	//   connPool: A connection pool that provides database connections.
	//   locker: A synchronization lock that is unlocked after initialization to avoid deadlocks.
	// Returns:
	//   *Stmt: A newly created statement object for executing SQL operations.
	//   error: An error if the statement preparation fails.
	New(ctx context.Context, key string, isTransaction bool, connPool ConnPool, locker sync.Locker) (*Stmt, error)

    Entry<K, V>[] entries2 = (Entry<K, V>[]) entries;
    return copyOf(Arrays.asList(entries2));
  }

  /**
   * Returns a new builder. The generated builder is equivalent to the builder created by the {@link
   * Builder} constructor.
   */
  public static <K, V> Builder<K, V> builder() {
    return new Builder<>();
  }

  /**

你可能之前已经了解到，你可以设置默认的[响应状态码](../tutorial/response-status-code.md)。

但在某些情况下，你需要返回一个不同于默认值的状态码。

## 使用场景 { #use-case }

例如，假设你想默认返回一个HTTP状态码为“OK”`200`。

但如果数据不存在，你想创建它，并返回一个HTTP状态码为“CREATED”`201`。

但你仍然希望能够使用`response_model`过滤和转换你返回的数据。

对于这些情况，你可以使用一个`Response`参数。

## 使用 `Response` 参数 { #use-a-response-parameter }

你可以在你的*路径操作函数*中声明一个`Response`类型的参数（就像你可以为cookies和头部做的那样）。

//     newerThan: "7d" # match objects newer than this value (e.g. 7d10h31s)
//     olderThan: "7d" # match objects older than this value (e.g. 7d10h31s)
//     createdAfter: "date" # match objects created after "date"
//     createdBefore: "date" # match objects created before "date"
//     tags:
//       - key: "name"
//         value: "pick*" # match objects with tag 'name', with all values starting with 'pick'
//     metadata:

    // unless it's actually going to be used; validate() is called for all set method calls, so it
    // needs to be fast.
    // (We could instead generate the message once, when the set is created, but zero is better.)
    if (!validator.get()) {
      throw new IllegalStateException(errorMessage.get());
    }
  }

                    <la:hidden property="id"/>
                    <la:hidden property="versionNo"/>
                </c:if>
                <la:hidden property="createdBy"/>
                <la:hidden property="createdTime"/>
                <la:hidden property="sortOrder"/>
                <div class="row">
                    <div class="col-md-12">
                        <div

            assertEquals(VALID_UUID_STRING, result.toUpperCase(), "toString() should return the correct UUID string in uppercase");
        }

        @Test
        @DisplayName("toString() should work correctly for UUID created from string")
        void testToStringFromConstructorWithString() {
            // Arrange
            UUID uuid = new UUID(VALID_UUID_STRING);

            // Act
            String result = uuid.toString();

MinIO needs a persistent volume to store configuration and application data. For testing purposes, you can launch MinIO by simply passing a directory (`/data` in the example below). This directory gets created in the container filesystem at the time of container start. But all the data is lost after container exits.

```sh
docker run \
  -p 9000:9000 \
  -p 9001:9001 \
  -e "MINIO_ROOT_USER=AKIAIOSFODNN7EXAMPLE" \