import jcifs.internal.SMBProtocolDecodingException;

/**
 * Response for SMB1 TRANS_TRANSACT_NAMED_PIPE transaction.
 *
 * This response contains the data returned from the named pipe
 * after a transact operation (write then read) has been completed.
 */
public class TransTransactNamedPipeResponse extends SmbComTransactionResponse {

    private final byte[] outputBuffer;

    /**

            // Some operations might succeed before key wipe, some might fail after
            // At minimum, we expect some activity (not all operations should be no-ops)
            int totalOperations = successCount.get() + failureCount.get();
            assertTrue(totalOperations > 0, "Some signing/verification operations should have been attempted");
        }

        @Test

クッキーを宣言するには、`Cookie`を使う必要があります。なぜなら、そうしないとパラメータがクエリのパラメータとして解釈されてしまうからです。

///

/// info | 情報

**ブラウザがクッキーを**特殊な方法で裏側で扱うため、**JavaScript** から簡単には触れられないことを念頭に置いてください。

`/docs` の **API docs UI** に移動すると、*path operation* のクッキーに関する **documentation** を確認できます。

しかし、データを **入力** して「Execute」をクリックしても、docs UI は **JavaScript** で動作するためクッキーは送信されず、値を何も書かなかったかのような **error** メッセージが表示されます。

///

## まとめ { #recap }

The normal (default) process, is as follows.

A `FastAPI` application (instance) has an `.openapi()` method that is expected to return the OpenAPI schema.

As part of the application object creation, a *path operation* for `/openapi.json` (or for whatever you set your `openapi_url`) is registered.

It just returns a JSON response with the result of the application's `.openapi()` method.

この**OpenAPI固有**の`examples`は、OpenAPI仕様の別のセクションに入ります。各JSON Schemaの中ではなく、**各*path operation*の詳細**に入ります。

そしてSwagger UIは、この特定の`examples`フィールドを以前からサポートしています。そのため、これを使って**ドキュメントUIに異なる例を表示**できます。

このOpenAPI固有フィールド`examples`の形は**複数の例**（`list`ではなく）を持つ`dict`であり、それぞれに追加情報が含まれ、その追加情報は**OpenAPI**にも追加されます。

これはOpenAPIに含まれる各JSON Schemaの中には入らず、外側の、*path operation*に直接入ります。

### `openapi_examples`パラメータの使用 { #using-the-openapi-examples-parameter }

enum ContextDevicePlacementPolicy {
  // Running operations with input tensors on the wrong device will fail.
  DEVICE_PLACEMENT_EXPLICIT = 0,
  // Copy the tensor to the right device but log a warning.
  DEVICE_PLACEMENT_WARN = 1,
  // Silently copy the tensor, which has a performance cost since the operation
  // will be blocked till the copy completes. This is the default policy.

   *
   * <p><b>Performance note:</b> This method will sometimes recognize that the actual copy operation
   * is unnecessary; for example, {@code copyOf(copyOf(anArrayList))} will copy the data only once.
   * This reduces the expense of habitually making defensive copies at API boundaries. However, the
   * precise conditions for skipping the copy operation are undefined.
   *
   * @throws NullPointerException if any of {@code elements} is null

            name = StringUtil.decamelize(this.getClass().getSimpleName().replace("Searcher", StringUtil.EMPTY)).toLowerCase(Locale.ENGLISH);
        }
        return name;
    }

    /**
     * Executes a search operation with the specified parameters.
     * This method must be implemented by concrete searcher classes.
     *
     * @param query the search query string

# Response Headers { #response-headers }

## Use a `Response` parameter { #use-a-response-parameter }

You can declare a parameter of type `Response` in your *path operation function* (as you can do for cookies).

And then you can set headers in that *temporal* response object.

{* ../../docs_src/response_headers/tutorial002_py310.py hl[1, 7:8] *}

And then you can return any object you need, as you normally would (a `dict`, a database model, etc).

import jcifs.util.Hexdump;

/**
 * SMB1 COM_RENAME command implementation.
 *
 * This command renames a file or directory on the SMB server.
 * It takes an old filename and new filename and performs the rename operation.
 */
public class SmbComRename extends ServerMessageBlock {

    private final int searchAttributes;
    private final String oldFileName;
    private final String newFileName;

    /**