String ts = ex.toString();
        assertTrue(ts.contains("SmbUnsupportedOperationException"), "toString should contain class name");
        assertTrue(ts.contains(ex.getMessage()), "toString should contain the detail message");
    }

    @ParameterizedTest(name = "Message preserved: [{0}]")
    @MethodSource("messages")
    @DisplayName("Message constructor preserves provided messages, including null/edge cases")

  std::vector<AbstractTensorHandle*> outputs;
  int expected_num_outputs = -1;
};

namespace tracing {

// =============================================================================
// Implementation detail for the unified execution APIs for Eager and tracing
// backends (graph/MLIR).
//
// This defines a set of abstract classes that are intended to provide the

        "&logFilter=(expression:'host.name:${nodeName}',kind:kuery)"
      buildFinished {
        link 'System metrics', "https://infra-stats.elastic.co/app/metrics/detail/host/" +
          "${nodeName}?_g=()&metricTime=(autoReload:!f,refreshInterval:5000," +
          "time:(from:${startTime - TimeUnit.MILLISECONDS.convert(5, TimeUnit.MINUTES)},interval:%3E%3D1m," +

For example, if the client tries to send a `tool` header with a value of `plumbus`, they will receive an **error** response telling them that the header parameter `tool` is not allowed:

```json
{
    "detail": [
        {
            "type": "extra_forbidden",
            "loc": ["header", "tool"],
            "msg": "Extra inputs are not permitted",
            "input": "plumbus",
        }
    ]
}
```

如果客户端尝试发送一些额外的数据，他们将收到**错误**响应。

例如，客户端尝试发送如下表单字段：

* `username`: `Rick`
* `password`: `Portal Gun`
* `extra`: `Mr. Poopybutthole`

他们将收到一条错误响应，表明字段 `extra` 不被允许：

```json
{
    "detail": [
        {
            "type": "extra_forbidden",
            "loc": ["body", "extra"],
            "msg": "Extra inputs are not permitted",
            "input": "Mr. Poopybutthole"
        }
    ]
}
```

```
org.gradle[.<qualifier>].<feature-name>.<detail>
```

The optional qualifier defines the secondary aspects, if any.

For better ergonomics on the CLI, some properties can have supplementary command-line build option(s).
The name of the feature in the build option SHOULD be the same as in the property name.

Shared scheme for long-form build options:

```
--<feature-name>-<detail>
```

* `username`: `Rick`
* `password`: `Portal Gun`
* `extra`: `Mr. Poopybutthole`

They will receive an error response telling them that the field `extra` is not allowed:

```json
{
    "detail": [
        {
            "type": "extra_forbidden",
            "loc": ["body", "extra"],
            "msg": "Extra inputs are not permitted",
            "input": "Mr. Poopybutthole"
        }
    ]
}
```

            },
            "HTTPValidationError": {
                "title": "HTTPValidationError",
                "type": "object",
                "properties": {
                    "detail": {
                        "title": "Detail",
                        "type": "array",
                        "items": {
                            "$ref": "#/components/schemas/ValidationError"
                        }

                        "title": "HTTPValidationError",
                        "type": "object",
                        "properties": {
                            "detail": {
                                "title": "Detail",
                                "type": "array",
                                "items": {
                                    "$ref": "#/components/schemas/ValidationError"

        assertTrue(npe.getMessage() == null || npe.getMessage().contains("reqPath"));
        verify(locator).handleDFSReferral(referral, null);
        verifyNoMoreInteractions(locator);
    }

    // Interaction detail: capture arguments passed to handleDFSReferral
    @Test
    @DisplayName("handleDFSReferral receives the exact arguments via captor")
    void handleDfsReferralArgumentCapture() {