assertEquals(SmbComTransaction.TRANS_WAIT_NAMED_PIPE, transWaitNamedPipe.getSubCommand());
    }

    @Test
    @DisplayName("Multiple wire format operations should be consistent")
    void testMultipleWireFormatOperations() {
        // Arrange
        transWaitNamedPipe = new TransWaitNamedPipe(mockConfig, testPipeName);

The same would happen if you had something like a <dfn title='A union between multiple types means "any of these types".'>union</dfn> between different types where one or more of them are not valid Pydantic types, for example this would fail 💥:

{* ../../docs_src/response_model/tutorial003_04_py310.py hl[8] *}

	return &StreamTypeHandler[Payload, Req, Resp]{id: h, InCapacity: 1, OutCapacity: 1}
}

// Register a handler for two-way streaming with payload, input stream and output stream.
// An optional subroute can be given. Multiple entries are joined with '/'.
func (h *StreamTypeHandler[Payload, Req, Resp]) Register(m *Manager, handle func(ctx context.Context, p Payload, in <-chan Req, out chan<- Resp) *RemoteErr, subroute ...string) error {

            assertTrue(true);
        } finally {
            // Restore original ClassLoader
            Thread.currentThread().setContextClassLoader(originalClassLoader);
        }
    }

    // Test multiple invocations of hook method
    @Test
    public void test_hook_multipleInvocations() {
        FwAssistantDirector assistantDirector = createMockAssistantDirector();

        // First invocation

/// tip

这里我们使用 [`time.perf_counter()`](https://docs.python.org/3/library/time.html#time.perf_counter) 而不是 `time.time()`，因为在这类场景中它可能更精确。🤓

///

## 多个中间件的执行顺序 { #multiple-middleware-execution-order }

当你使用 `@app.middleware()` 装饰器或 `app.add_middleware()` 方法添加多个中间件时，每个新中间件都会包裹应用，形成一个栈。最后添加的中间件是“最外层”的，最先添加的是“最内层”的。

在请求路径上，最外层的中间件先运行。

在响应路径上，它最后运行。

例如：

```Python

        assertNotNull(lastParams);
        assertEquals(scriptExecutor, lastParams.get("executor"));
    }

    @Test
    public void test_execute_withMultipleEngines() {
        // Setup multiple script engines
        TestScriptEngine engine1 = new TestScriptEngine("engine1");
        TestScriptEngine engine2 = new TestScriptEngine("engine2");
        scriptEngineFactory.add("type1", engine1);

        CountDownLatch endLatch = new CountDownLatch(threadCount);
        AtomicInteger successCount = new AtomicInteger(0);
        List<Exception> exceptions = new ArrayList<>();

        // When - Multiple threads get and release buffers
        for (int t = 0; t < threadCount; t++) {
            executor.submit(() -> {
                try {
                    startLatch.await();

 * <pre>
 * new EqualsTester().addEqualityGroup(foo).testEquals();
 * </pre>
 *
 * <p>This tests {@code foo.equals(foo)}, {@code foo.equals(null)}, and a few other operations.
 *
 * <p>For more extensive testing, add multiple equality groups. Each group should contain objects
 * that are equal to each other but unequal to the objects in any other group. For example:
 *
 * <pre>
 * new EqualsTester()

        }

        @Test
        @DisplayName("Should support multiple method invocations")
        void shouldSupportMultipleInvocations() {
            ACE ace = mock(ACE.class);
            when(ace.getAccessMask()).thenReturn(ACE.GENERIC_ALL);
            when(ace.isAllow()).thenReturn(true);

            // Multiple calls to same method
            ace.getAccessMask();
            ace.getAccessMask();

 * reduce contention. Method {@link #sum} (or, equivalently, {@link #longValue}) returns the current
 * total combined across the variables maintaining the sum.
 *
 * <p>This class is usually preferable to {@link AtomicLong} when multiple threads update a common
 * sum that is used for purposes such as collecting statistics, not for fine-grained synchronization
 * control. Under low update contention, the two classes have similar characteristics. But under