* {@link NdrBuffer#enc_ndr_hyper(long)} and {@link NdrBuffer#dec_ndr_hyper()}.
 * The tests verify that:
 * <ul>
 *   <li>encoding and decoding round‑trip correctly handle typical, zero,
 *       and extreme {@code long} values.</li>
 *   <li>encode/decode methods interact correctly with a mocked
 *       {@link NdrBuffer} so that the correct method is called with

When a WebSocket connection is closed, the `await websocket.receive_text()` will raise a `WebSocketDisconnect` exception, which you can then catch and handle like in this example.

{* ../../docs_src/websockets/tutorial003_py39.py hl[79:81] *}

To try it out:

* Open the app with several browser tabs.
* Write messages from them.
* Then close one of the tabs.

 */
public class MsrpcQueryInformationPolicy extends lsarpc.LsarQueryInformationPolicy {

    /**
     * Constructs a new MsrpcQueryInformationPolicy request.
     *
     * @param policyHandle the policy handle obtained from LsarOpenPolicy
     * @param level the information level to query
     * @param info the NdrObject to receive the policy information
     */

      if (!response.isSuccessful) throw IOException("Unexpected code $response")

      println(response.body.string())
    }
  }
}

object ConsoleCallbackHandler : CallbackHandler {
  override fun handle(callbacks: Array<Callback>) {
    for (callback in callbacks) {
      if (callback is PasswordCallback) {
        val console = System.console()

        if (console != null) {

            // When
            SmbWatchHandle watchHandle = mockResource.watch(filter, true);

            // Then
            assertNotNull(watchHandle, "Watch handle should not be null");
            assertSame(mockWatchHandle, watchHandle, "Should return expected watch handle");
        }
    }

    @Nested
    @DisplayName("Security Operations Tests")
    class SecurityOperationsTests {

        @Test

 *
 *  * [TCP handshake][connectSocket]
 *  * Optional [CONNECT tunnels][connectTunnel]. When using an HTTP proxy to reach an HTTPS server
 *    we must send a `CONNECT` request, and handle authorization challenges from the proxy.
 *  * Optional [TLS handshake][connectTls].
 *
 * Each step may fail. If a retry is possible, a new instance is created with the next plan, which
 * will be configured differently.
 */

    extends AbstractFuture<V> {
  /*
   * In the GWT versions of the methods (below), every exceptionType parameter is required to be
   * Class<Throwable>. To handle only certain kinds of exceptions under GWT, you'll need to write
   * your own instanceof tests.
   */

  public final FluentFuture<V> catching(
      Class<Throwable> exceptionType,

        }
    }

    @Nested
    @DisplayName("Edge Cases and Boundary Tests")
    class EdgeCaseTests {

        @Test
        @DisplayName("Should handle encoding at buffer boundary")
        void testEncodingAtBufferBoundary() {
            byte[] smallBuffer = new byte[24];
            lock = new Smb2Lock(100L, 200L, 1);

When deploying applications you will probably want to have some **replication of processes** to take advantage of **multiple cores** and to be able to handle more requests.

As you saw in the previous chapter about [Deployment Concepts](concepts.md){.internal-link target=_blank}, there are multiple strategies you can use.

If you integrate your API with an OAuth2 provider, you will be able to authenticate and come back to the API docs with the acquired credentials. And interact with it using the real OAuth2 authentication.

Swagger UI will handle it behind the scenes for you, but it needs this "redirect" helper.

///

### Create a *path operation* to test it { #create-a-path-operation-to-test-it }