//                                                                           =========
    /** The time manager for handling time-related operations. */
    @Resource
    private TimeManager timeManager;

    /** The async manager for handling asynchronous operations. */
    @Resource
    private AsyncManager asyncManager;

    /** The session manager for handling user sessions. */
    @Resource

import com.google.common.annotations.J2ktIncompatible;
import java.math.BigInteger;
import org.jspecify.annotations.Nullable;

/**
 * A wrapper class for unsigned {@code int} values, supporting arithmetic operations.
 *
 * <p>In some cases, when speed is more important than code readability, it may be faster simply to
 * treat primitive {@code int} values as unsigned, using the methods from {@link UnsignedInts}.
 *

//     <S3ConcurrentTaskLimit>
//
//   - Defines how many S3 operations are executed parallel within one Repository Task Slot (and within one backup object
//     that gets offloaded). The same registry key setting overwrites the storage-defined setting.
//     Optional value, default 64, range: 1-unlimited
//
//   - <S3MultiObjectDeleteLimit>
//     Some of the Veeam products use Multi Delete operations. This setting can reduce how many objects are included in one

* `@app.get()`
* `@app.post()`
* `@app.put()`
* `@app.delete()`
* etc.

{* ../../docs_src/response_status_code/tutorial001_py39.py hl[6] *}

/// note

Notice that `status_code` is a parameter of the "decorator" method (`get`, `post`, etc). Not of your *path operation function*, like all the parameters and body.

///

        dep -->> dep: Raise other exception
    end
    dep ->> operation: Run dependency, e.g. DB session
    opt raise
        operation -->> handler: Raise HTTPException
        handler -->> client: HTTP error response
        operation -->> dep: Raise other exception
    end
    operation ->> client: Return response to client
    Note over client,operation: Response is already sent, can't change it anymore
    opt Tasks

But you can return a `JSONResponse` directly from your *path operations*.

It might be useful, for example, to return custom headers or cookies.

## Return a `Response` { #return-a-response }

In fact, you can return any `Response` or any sub-class of it.

/// tip

`JSONResponse` itself is a sub-class of `Response`.

///

            assertArrayEquals(new byte[] { 1, 2, 3, 4 }, handle.getSessionKey());
        }
    }

    @Nested
    @DisplayName("Bind Operation Tests")
    class BindOperationTests {

        @Test
        @DisplayName("Should execute bind operation successfully")
        void testBindSuccess() throws DcerpcException, IOException {
            // Given: Spy to intercept sendrecv calls

#### Figure 2 - KMS key hierarchy

```
                                                          CMK (master key)
                                                           |

	// Status of resync operation
	ResyncStatus string `json:"resyncStatus,omitempty"`
	// Completed size in bytes
	ReplicatedSize int64 `json:"completedReplicationSize"`
	// Failed size in bytes
	FailedSize int64 `json:"failedReplicationSize"`
	// Total number of failed operations
	FailedCount int64 `json:"failedReplicationCount"`
	// Total number of failed operations
	ReplicatedCount int64 `json:"replicationCount"`

        protected Writer writer;

        /** The mapping item being updated, or null for read-only operations. */
        protected CharMappingItem item;

        /**
         * Constructs a new MappingUpdater for handling file updates.
         *
         * @param newItem the character mapping item to update, or null for read-only operations
         */
        protected MappingUpdater(final CharMappingItem newItem) {