@Mock
    private Configuration mockConfig;

    private TransCallNamedPipe transCallNamedPipe;
    private static final String TEST_PIPE_NAME = "\\\\PIPE\\\\testpipe";
    private static final byte[] TEST_DATA = "Test pipe data".getBytes();

    @BeforeEach
    void setUp() {
        MockitoAnnotations.openMocks(this);
    }

    @Test
    @DisplayName("Test constructor initializes fields correctly")

                            <div class="card-footer">
                                <button type="button" class="btn btn-warning ${f:h(editableClass)}"
                                        data-toggle="modal" data-target="#confirmToRebuildConfigIndex">
                                    <i class="fa fa-sync" aria-hidden="true"></i>
                                    <la:message key="labels.rebuild_config_index_button"/>

                                                       items="${pathMappingItems}">
                                                <tr
                                                        data-href="${contextPath}/admin/pathmap/details/4/${f:u(data.id)}" role="button" tabindex="0">
                                                    <td>${f:h(data.regex)}</td>

abstract class GeneratePlatformsDataTask : DefaultTask() {

    data class PlatformData(val name: String, val dirs: List<String>, val uses: List<String>)

    @get:OutputFile
    abstract val outputFile: RegularFileProperty

    @get:Input
    abstract val platforms: ListProperty<Platform>

    @TaskAction
    fun action() {
        val allPlatforms = platforms.get()
        val data = allPlatforms.map { platform ->
            PlatformData(

///

## Server-Sent Events란 { #what-are-server-sent-events }

SSE는 서버에서 클라이언트로 HTTP를 통해 데이터를 스트리밍하기 위한 표준입니다.

각 이벤트는 `data`, `event`, `id`, `retry`와 같은 "필드"를 가진 작은 텍스트 블록이며, 빈 줄로 구분됩니다.

다음과 같습니다:

```
data: {"name": "Portal Gun", "price": 999.99}

data: {"name": "Plumbus", "price": 32.99}

```

SSE는 AI 채팅 스트리밍, 실시간 알림, 로그와 관측성, 그리고 서버가 클라이언트로 업데이트를 푸시하는 여러 경우에 흔히 사용됩니다.

/// tip | 팁

```

Then load the policy via OPA's REST API.

```
curl -X PUT --data-binary @example.rego \
  localhost:8181/v1/policies/putobject
```

### 4. Setup MinIO with OPA

Set the `MINIO_POLICY_PLUGIN_URL` as the endpoint that MinIO should send authorization requests to. Then start the server.

```sh
export MINIO_POLICY_PLUGIN_URL=http://localhost:8181/v1/data/httpapi/authz/allow
export MINIO_CI_CD=1
export MINIO_ROOT_USER=minio

./mc ready minio1 --insecure
./mc ready minio2 --insecure

# Prepare data for tests
echo -n "Preparing test data ..."
mkdir -p /tmp/data
echo "Hello from encrypted world" >/tmp/data/encrypted
touch /tmp/data/mpartobj
shred -s 500M /tmp/data/mpartobj
touch /tmp/data/defpartsize
shred -s 500M /tmp/data/defpartsize
touch /tmp/data/custpartsize
shred -s 500M /tmp/data/custpartsize
echo "done"

# Add replication site

 * Implementations can specify how long cached data should be retained.
 *
 * @since 4.0.0
 */
@Experimental
public interface CacheMetadata {

    /**
     * Returns the cache retention that should be applied to the associated data.
     *
     * @return The CacheRetention indicating how long data should be retained, or null if
     *         no specific cache retention is defined
     */

    person_data = {"name": "Dive", "lastname": "Wilson"}
    response = client.post("/people/", json=person_data)
    data = response.json()
    assert response.status_code == 200, response.text
    assert data["name"] == person_data["name"]
    assert data["lastname"] == person_data["lastname"]

    }

    /**
     * Processes a document through the ingest pipeline.
     * Applies all available ingesters to transform the document data.
     *
     * @param paramMap the data store parameters
     * @param dataMap the document data to process
     * @return the processed document data
     */
    protected Map<String, Object> ingest(final DataStoreParams paramMap, final Map<String, Object> dataMap) {