// When & Then - test boundary conditions
        // Negative length or offset should not cause issues (len <= 0 returns early)
        assertDoesNotThrow(() -> outputStream.write(data, 0, -1)); // negative length, returns early
        assertDoesNotThrow(() -> outputStream.write(data, 0, 0)); // zero length, returns early

        // These should pass through to the underlying implementation

            public String getSlackWebhookUrls() {
                return "";
            }
        });

        MockSMailPostingDiscloser discloser = new MockSMailPostingDiscloser();

        // Should return early without doing anything
        try {
            notificationHelper.sendToSlack(null, discloser);
        } catch (Exception e) {
            fail("sendToSlack() should not throw an exception with blank URLs: " + e.getMessage());

            });
            readerThreads[i].start();
        }

        // Writer thread sets alive to false early
        Thread writerThread = new Thread(() -> {
            try {
                startLatch.await(); // Wait for start signal
                // Set alive to false very early - no delay
                dataStore.alive = false;
            } catch (InterruptedException e) {

        assertTrue("SuggesterException should have been thrown", exceptionThrown);
    }

    /**
     * Test switchIndex when update and search indices are the same.
     * Verifies that the method returns early without errors.
     */
    @Test
    public void testSwitchIndex_sameUpdateAndSearchIndex() throws Exception {
        final Suggester suggester = Suggester.builder().build(client, "same-index-test");

        final String sessionId = "session5";
        final List<String> emptyList = Collections.emptyList();

        // Should not throw exception when adding empty list
        // This validates the early return optimization
        try {
            urlFilterService.addIncludeUrlFilter(sessionId, emptyList);
        } catch (final Exception e) {
            fail();
        }

 * Tasks execute with the same happens-before order that the function calls to {@link #submit} and
 * {@link #submitAsync} that submitted those tasks had.
 *
 * <p>This class has limited support for cancellation and other "early completions":
 *
 * <ul>
 *   <li>While calls to {@code submit} and {@code submitAsync} return a {@code Future} that can be
 *       cancelled, cancellation never propagates to a task that has started to run -- neither to

    }

    @Test
    @DisplayName("ensureDFSResolved returns early for SmbComClose requests")
    void ensureDFSResolved_closeRequest_noop() throws Exception {
        SmbTreeConnection c = spy(newConn());
        SmbResourceLocatorImpl loc = new SmbResourceLocatorImpl(ctx, smbUrl("smb://server/share/"));

        // Using a SmbComClose instance triggers early return without DFS/session work

///

## Early exit and `scope` { #early-exit-and-scope }

Normally the exit code of dependencies with `yield` is executed **after the response** is sent to the client.

そして、`Depends(scope="request")`（デフォルト）を使う場合、`yield` の後の終了コードはレスポンス送信後に実行されます。

詳しくはドキュメント「[`yield` を使う依存関係 - 早期終了と `scope`](../tutorial/dependencies/dependencies-with-yield.md#early-exit-and-scope)」を参照してください。

### `yield` と `StreamingResponse` を伴う依存関係、技術詳細 { #dependencies-with-yield-and-streamingresponse-technical-details }

            associated with a Maven project can lack a file. As such, this annotation is meant for Mojos that only
            want to analyze the set of transitive dependencies, in particular during early lifecycle phases where
            full dependency resolution might fail due to projects which haven't been built yet.
          </description>
        </field>
        <field>
          <name>dependencyCollection</name>