}

    @Test
    @DisplayName("available() on SMB2 returns peeked byte count and interacts with tree")
    void available_smb2_happyPath() throws Exception {
        // Verify SMB2 path: IOCTL peek result is returned and resources are closed
        SmbPipeInputStream stream = newStreamWithMinimalStubs(true);

        // Arrange mocks for available()
        when(handle.ensureOpen()).thenReturn(fd);

	"io"
	"log"
	"os"
	"os/exec"
	"path/filepath"
	"regexp"
	"runtime"
	"slices"
	"strconv"
	"strings"
	"sync"
	"testing"
)

const verbose = false

func goCmd() string {
	var exeSuffix string
	if runtime.GOOS == "windows" {
		exeSuffix = ".exe"
	}
	path := filepath.Join(testenv.GOROOT(nil), "bin", "go"+exeSuffix)
	if _, err := os.Stat(path); err == nil {
		return path
	}
	return "go"

Because it's a Python exception, you don't `return` it, you `raise` it.

This also means that if you are inside a utility function that you are calling inside of your *path operation function*, and you raise the `HTTPException` from inside of that utility function, it won't run the rest of the code in the *path operation function*, it will terminate that request right away and send the HTTP error from the `HTTPException` to the client.

        assertTrue(ex.getMessage().contains("Watch was broken by tree disconnect"));
    }

    // Happy path for SMB2: a response is received and the list is returned; tree is closed
    @Test
    @DisplayName("watch() SMB2 happy path returns notifications and closes tree")
    void watch_smb2_success_returnsList_andClosesTree() throws Exception {

                .build();
    }

    @Nonnull
    static ModelBuilderRequest build(@Nonnull Session session, @Nonnull Path path) {
        return builder()
                .session(requireNonNull(session, "session cannot be null"))
                .source(Sources.buildSource(path))
                .build();
    }

    @Nonnull
    static ModelBuilderRequestBuilder builder() {

        String filename = "\\\\server\\share\\file.txt";
        trans2GetDfsReferral = new Trans2GetDfsReferral(mockConfig, filename);

        // Set path field (inherited from parent)
        Field pathField = trans2GetDfsReferral.getClass().getSuperclass().getSuperclass().getDeclaredField("path");
        pathField.setAccessible(true);
        pathField.set(trans2GetDfsReferral, filename);

        // When

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE components PUBLIC "-//DBFLUTE//DTD LastaDi 1.0//EN"
	"http://dbflute.org/meta/lastadi10.dtd">
<components namespace="fessCrawler">
	<include path="crawler/container.xml" />

	<component name="logHelper"
		class="org.codelibs.fess.helper.CrawlerLogHelper">
	</component>

            int rn) throws CIFSException {
        if (log.isDebugEnabled()) {
            log.debug("Resolving DFS path " + path);
        }

        if (path.length() >= 2 && path.charAt(0) == '\\' && path.charAt(1) == '\\') {
            throw new SmbException("Path must not start with double slash: " + path);
        }

     * </p>
     *
     * @param rootDir the root directory (must not be {@literal null})

If you have quite some technical knowledge (coroutines, threads, blocking, etc.) and are curious about how FastAPI handles `async def` vs normal `def`, go ahead.

///

### Path operation functions { #path-operation-functions }

When you declare a *path operation function* with normal `def` instead of `async def`, it is run in an external threadpool that is then awaited, instead of being called directly (as it would block the server).