return true
		}
		if cs[j].after == "*" && cs[i].after != "*" {
			return true
		}
		return false
	})

	for _, c := range cs {
		// show warning message the callback name already exists
		if idx := getRIndex(names, c.name); idx > -1 && !c.replace && !c.remove && !cs[idx].remove {

/*
 * Copyright 2012-2025 CodeLibs Project and the Others.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,

            SmbResourceLocator locator = resource.getLocator();

            // Then
            assertNotNull(locator, "Locator should not be null");
            assertSame(mockLocator, locator, "Should return the expected locator");
        }

        @Test
        @DisplayName("getContext should return CIFSContext")
        void testGetContext() throws CIFSException {
            // Given

    }

    @Test
    @DisplayName("Test toString method")
    void testToString() {
        String result = transaction.toString();

        assertNotNull(result);
        // The toString method from parent class returns SMB_COM_TRANSACTION, not SmbComTransaction
        assertTrue(result.contains("SMB_COM_TRANSACTION"));
        // Also verify it contains transaction-specific details

/// warning

請注意，由於 Pydantic 團隊自 Python 3.14 起不再支援 Pydantic v1，因此在 Python 3.14 及以上版本中也不支援使用 `pydantic.v1`。

///

### 同一應用同時使用 Pydantic v1 與 v2 { #pydantic-v1-and-v2-on-the-same-app }

Pydantic 不支援在 Pydantic v2 模型的欄位中使用 Pydantic v1 模型，反之亦然。

```mermaid
graph TB
    subgraph "❌ Not Supported"
        direction TB
        subgraph V2["Pydantic v2 Model"]

        void testLockSequenceInformation() {
            // Note: lockSequenceNumber and lockSequenceIndex are private and not settable
            // They default to 0, so we test the default encoding
            byte[] buffer = new byte[256];
            request.writeBytesWireFormat(buffer, 0);

            int lockSequence = SMBUtil.readInt4(buffer, 4);

    @Mock
    private SmbResource parent;

    @Mock
    private SmbResource resource;

    @Mock
    private FileEntry fileEntry;

    /**
     * Test implementation that always returns the same mock resource
     */
    private class TestIterator extends FileEntryAdapterIterator {
        TestIterator(ResourceFilter filter) {
            super(parent, delegate, filter);
        }

        @Override

        with:
          key: avd-${{ runner.os }}-${{ matrix.api-level }}-${{ matrix.api-level >= 30 && 'x86_64' || 'x86' }}
          path: |
            ~/.android/avd/*
            ~/.android/adb*
            # Added the actual system image path
            ${{ env.ANDROID_HOME }}/system-images/android-${{ matrix.api-level }}

      - name: Create AVD and generate snapshot for caching
        if: steps.avd-cache.outputs.cache-hit != 'true'

# 类作为依赖项 { #classes-as-dependencies }

在深入探究 **依赖注入** 系统之前，让我们升级之前的例子。

## 来自前一个例子的`dict` { #a-dict-from-the-previous-example }

在前面的例子中, 我们从依赖项 ("可依赖对象") 中返回了一个 `dict`:

{* ../../docs_src/dependencies/tutorial001_an_py310.py hl[9] *}

但是后面我们在路径操作函数的参数 `commons` 中得到了一个 `dict`。

我们知道编辑器不能为 `dict` 提供很多支持(比如补全)，因为编辑器不知道 `dict` 的键和值类型。

对此，我们可以做的更好...

## 什么构成了依赖项 { #what-makes-a-dependency }

到目前为止，你看到的依赖项都被声明为函数。

        when(tree.isSMB2()).thenReturn(false);
        when(tree.getConfig()).thenReturn(config);
        when(config.getPid()).thenReturn(1234);

        // Stub send to populate the provided response instance via reflection
        Mockito.doAnswer(inv -> {
            Object resp = inv.getArgument(1);