* at the end of the test, so there is no object state put at risk by stopping the threads
   * abruptly. In other cases, a test may put a thread into an uninterruptible operation
   * intentionally, so there is no other way to clean up these threads. (The better solution,
   * though, would be to run the tests that use TestThread in separate VMs so that their threads

        return getProperties().remove(key);
    }

    @Override
    public void save(final OutputStream out, final String comments) {
        throw new UnsupportedOperationException("Unsupported operation.");
    }

    @Override
    public Object setProperty(final String key, final String value) {
        return getProperties().setProperty(key, value);
    }

    @Override
    public int size() {

		return
	}

	pools, ok := objectAPI.(*erasureServerPools)
	if !ok {
		writeErrorResponseJSON(ctx, w, errorCodes.ToAPIErr(ErrNotImplemented), r.URL)
		return
	}

	// Cancel any ongoing rebalance operation
	globalNotificationSys.StopRebalance(r.Context())
	writeSuccessResponseHeadersOnly(w)
	adminLogIf(ctx, pools.saveRebalanceStats(GlobalContext, 0, rebalSaveStoppedAt))
	globalNotificationSys.LoadRebalanceMeta(ctx, false)

        @Override
        public int getOpnum() {
            return 0x0f;
        }

        /** Return value from the RPC call. */
        public int retval;
        /** Policy handle for the LSA operation. */
        public rpc.policy_handle handle;
        /** Array of SIDs to lookup. */
        public LsarSidArray sids;
        /** Referenced domain list returned from lookup. */

Commencez par créer un nouveau `APIRouter` qui contiendra un ou plusieurs callbacks.

{* ../../docs_src/openapi_callbacks/tutorial001_py310.py hl[1,23] *}

### Créer le *chemin d'accès* du callback { #create-the-callback-path-operation }

Pour créer le *chemin d'accès* du callback, utilisez le même `APIRouter` que vous avez créé ci-dessus.

Il devrait ressembler exactement à un *chemin d'accès* FastAPI normal :

### 태그 사용 { #use-your-tags }

`tags` 매개변수를 *경로 처리* (및 `APIRouter`)와 함께 사용하여 이를 서로 다른 태그에 할당하세요:

{* ../../docs_src/metadata/tutorial004_py310.py hl[21,26] *}

/// info | 정보

태그에 대한 자세한 내용은 [경로 처리 구성](path-operation-configuration.md#tags)에서 읽어보세요.

///

### 문서 확인 { #check-the-docs }

이제 문서를 확인하면 모든 추가 메타데이터가 표시됩니다:

<img src="/img/tutorial/metadata/image02.png">

### 태그 순서 { #order-of-tags }

///

### 创建回调的 `APIRouter` { #create-a-callback-apirouter }

首先，新建包含一些用于回调的 `APIRouter`。

{* ../../docs_src/openapi_callbacks/tutorial001_py310.py hl[1,23] *}

### 创建回调*路径操作* { #create-the-callback-path-operation }

创建回调*路径操作*也使用之前创建的 `APIRouter`。

它看起来和常规 FastAPI *路径操作*差不多：

* 声明要接收的请求体，例如，`body: InvoiceEvent`
* 还要声明要返回的响应，例如，`response_model=InvoiceEventReceived`

			if errors.Is(err, errFileNotFound) || errors.Is(err, errFileCorrupt) {
				if derr == nil {
					derr = err
				}
			}
		} else if err != nil {
			// For all errors that cannot be reconstructed fail the read operation.
			return -1, err
		}

		if err = e.DecodeDataBlocks(bufs); err != nil {
			return -1, err
		}

		n, err := writeDataBlocks(ctx, writer, bufs, e.dataBlocks, blockOffset, blockLength)

	volume string
	paths  []string
	opsID  string
}

// NewNSLock - returns a lock instance for a given volume and
// path. The returned lockInstance object encapsulates the nsLockMap,
// volume, path and operation ID.
func (n *nsLockMap) NewNSLock(lockers func() ([]dsync.NetLocker, string), volume string, paths ...string) RWLocker {
	sort.Strings(paths)
	opsID := mustGetUUID()
	if n.isDistErasure {

    //                                               -------
    /**
     * Displays the details of a web authentication configuration.
     *
     * @param crudMode the CRUD mode for the operation
     * @param id the ID of the web authentication to display
     * @return HTML response for the web authentication details page
     */
    @Execute
    @Secured({ ROLE, ROLE + VIEW })