*
 * There is no benefit to invoking multiple `close()` methods for the same response body.
 *
 * For synchronous calls, the easiest way to make sure a response body is closed is with a `try`
 * block. With this structure the compiler inserts an implicit `finally` clause that calls
 * [close()][Response.close] for you.
 *
 * ```java
 * Call call = client.newCall(request);
 * try (Response response = call.execute()) {

  <span style="background-color:#009485"><font color="#D3D7CF"> FastAPI </font></span>  Starting production server 🚀

             Searching for package file structure from directories with
             <font color="#3465A4">__init__.py</font> files
             Importing from <font color="#75507B">/home/user/code/</font><font color="#AD7FA8">awesomeapp</font>

```console
$ <font color="#4E9A06">fastapi</font> run <u style="text-decoration-style:solid">main.py</u>
<span style="background-color:#009485"><font color="#D3D7CF"> FastAPI </font></span>  Starting server
        Searching for package file structure
```

...ve bir başka console code örneği...

```console
// "Code" adında bir dizin oluştur
$ mkdir code
// O dizine geç
$ cd code
```

...ve bir Python code örneği...

```Python

// when it has been returned on a handler.
// This will disable automatic response recycling/pooling.
// Typically this is used when the response sharing part of its data structure.
func (h *SingleHandler[Req, Resp]) WithSharedResponse() *SingleHandler[Req, Resp] {
	h.sharedResp = true
	return h
}

// NewResponse creates a new response.

import com.google.common.annotations.J2ktIncompatible;
import java.io.Serializable;
import java.util.NoSuchElementException;
import org.jspecify.annotations.Nullable;

/**
 * Implementation detail for the internal structure of {@link Range} instances. Represents a unique
 * way of "cutting" a "number line" (actually of instances of type {@code C}, not necessarily

Since the name of the property is the primary source of immediate information for users, both the names themselves and their structure should convey enough information to set the right expectations.

Previously, there was no formalization of property naming; only loose conventions were followed.

import com.google.common.annotations.J2ktIncompatible;
import java.io.Serializable;
import java.util.NoSuchElementException;
import org.jspecify.annotations.Nullable;

/**
 * Implementation detail for the internal structure of {@link Range} instances. Represents a unique
 * way of "cutting" a "number line" (actually of instances of type {@code C}, not necessarily

import com.google.common.annotations.GwtCompatible;
import com.google.common.collect.ImmutableList;
import java.util.List;
import org.jspecify.annotations.Nullable;

/**
 * A memory-efficient binary trie structure for public suffix lookups. The trie is stored as a
 * series of 16-bit characters in a String.
 *
 * <p>The trie data is stored in a {@link CharSequence} where each node takes 3 characters:
 *
 * <ol>

        assertNull(result2);
    }

    @Test
    void testGetSecurityWithSpecialCharactersInSecurityDescriptor() throws Exception {
        // Test with security descriptor containing special byte values but invalid structure
        srvsvc.ShareInfo502 info502 = new srvsvc.ShareInfo502();
        byte[] specialBytes = new byte[] { 0, -1, 127, -128, 64 };
        info502.security_descriptor = specialBytes;

    // Base64 encoded Type 3 message: NTLMSSP, Type 3
    // User: "user", Domain: "DOMAIN", Workstation: "WORKSTATION"
    // This is a valid Type 3 message with proper structure
    private final String type3MessageBase64 = createValidType3Message();

    /**
     * Creates a valid Type 3 NTLM message for testing
     */
    private static String createValidType3Message() {