* etcd: stop watcher when watch channel is closed ([#33003](https://github.com/kubernetes/kubernetes/pull/33003), [@hongchaodeng](https://github.com/hongchaodeng))
* etcd3: dereference the UID pointer for a readable error message. ([#33349](https://github.com/kubernetes/kubernetes/pull/33349), [@madhusudancs](https://github.com/madhusudancs))

        Configuration responseConfig = (Configuration) configField.get(response);
        assertEquals(mockConfig, responseConfig);
    }

    @Test
    @DisplayName("size should return correct message size")
    void testSize() {
        int expectedSize = Smb2Constants.SMB2_HEADER_LENGTH + 24;
        // size8 method rounds up to 8-byte boundary
        int expectedAlignedSize = (expectedSize + 7) & ~7;

Але вона буде оброблена функцією-обробником `unicorn_exception_handler`.

Отже, ви отримаєте зрозумілу помилку з кодом статусу HTTP `418` і JSON-вмістом:

```JSON
{"message": "Oops! yolo did something. There goes a rainbow..."}
```

/// note | Технічні деталі

Ви також можете використовувати `from starlette.requests import Request` і `from starlette.responses import JSONResponse`.

Namun bu, `unicorn_exception_handler` tarafından handle edilir.

Böylece HTTP status code’u `418` olan, JSON içeriği şu şekilde temiz bir hata response’u alırsınız:

```JSON
{"message": "Oops! yolo did something. There goes a rainbow..."}
```

/// note | Teknik Detaylar

`from starlette.requests import Request` ve `from starlette.responses import JSONResponse` da kullanabilirsiniz.

{* ../../docs_src/path_params/tutorial005_py310.py hl[18,21,23] *}

İstemcinizde şöyle bir JSON response alırsınız:

```JSON
{
  "model_name": "alexnet",
  "message": "Deep Learning FTW!"
}
```

## Path İçeren Path Parametreleri { #path-parameters-containing-paths }

Diyelim ki `/files/{file_path}` path'ine sahip bir *path operation*'ınız var.

        NullPointerException exception = assertThrows(NullPointerException.class, () -> {
            smbComTreeDisconnect = new SmbComTreeDisconnect(null);
        });

        // Verify the exception message indicates the config is null
        assertTrue(exception.getMessage().contains("config"));
    }

    /**
     * Test constructor with mock configuration
     */
    @Test

这里，请求 `/unicorns/yolo` 时，路径操作会触发 `UnicornException`。

但该异常将会被 `unicorn_exception_handler` 处理。

你会收到清晰的错误信息，HTTP 状态码为 `418`，JSON 内容如下：

```JSON
{"message": "Oops! yolo did something. There goes a rainbow..."}
```

/// note | 技术细节

也可以使用 `from starlette.requests import Request` 和 `from starlette.responses import JSONResponse`。

                                    "anyOf": [{"type": "string"}, {"type": "integer"}]
                                },
                            },
                            "msg": {"title": "Message", "type": "string"},
                            "type": {"title": "Error Type", "type": "string"},
                            "input": {"title": "Input"},

import org.apache.hc.core5.http.ClassicHttpResponse;
import org.apache.hc.core5.http.HttpEntity;
import org.apache.hc.core5.http.HttpHost;
import org.apache.hc.core5.http.HttpRequest;
import org.apache.hc.core5.http.message.BasicNameValuePair;
import org.apache.hc.core5.http.protocol.HttpContext;
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
import org.codelibs.core.exception.IORuntimeException;

    val fakeAuthChallengeResponse =
      Response
        .Builder()
        .request(proxyConnectRequest)
        .protocol(Protocol.HTTP_1_1)
        .code(HttpURLConnection.HTTP_PROXY_AUTH)
        .message("Preemptive Authenticate")
        .sentRequestAtMillis(-1L)
        .receivedResponseAtMillis(-1L)
        .header("Proxy-Authenticate", "OkHttp-Preemptive")
        .build()

    val authenticatedRequest =