delete[] dims;

  TF_TString* data = static_cast<TF_TString*>(TF_TensorData(t));
  for (int i = 0; i < batch_size; ++i) {
    TF_TString_Init(&data[i]);
    // The following input string length is large enough to make sure that
    // copy to tstring in large mode.
    std::string source =
        "This is the " + std::to_string(i + 1) + "th. data element\n";
    TF_TString_Copy(&data[i], source.c_str(), source.length());
  }

                                <c:if test="${editable}">
                                    <button type="button" class="btn btn-danger" name="delete"
                                            data-toggle="modal" data-target="#confirmToDelete"
                                            value="<la:message key="labels.joblog_button_delete" />">
                                        <em class="fa fa-trash">

We are not restricted to having only one dependency that can return that type of data.

///

## Other models { #other-models }

You can now get the current user directly in the *path operation functions* and deal with the security mechanisms at the **Dependency Injection** level, using `Depends`.

And you can use any model or data for the security requirements (in this case, a Pydantic model `User`).

    }

    @Test
    void testWriteOctetArray() {
        byte[] data = { 0x01, 0x02, 0x03, 0x04 };
        ndrBuffer.writeOctetArray(data, 0, data.length);

        assertEquals(data.length, ndrBuffer.getIndex());
        assertEquals(data.length, ndrBuffer.getLength());
        assertArrayEquals(data, Arrays.copyOfRange(buffer, 0, data.length));

        // Write with offset and length
        ndrBuffer.setIndex(10);

    * Doğrulayıcılar en kompleks data şemalarının bile temiz ve kolay bir şekilde tanımlanmasına izin veriyor, ve hepsi JSON şeması olarak dokümante ediliyor
    * Pydantic, JSON objen ne kadar derin (nested) olursa olsun doğrulamasını ve gösterimini yapıyor
* **Genişletilebilir**:

These handlers are in charge of returning the default JSON responses when you `raise` an `HTTPException` and when the request has invalid data.

You can override these exception handlers with your own.

### Override request validation exceptions { #override-request-validation-exceptions }

When a request contains invalid data, **FastAPI** internally raises a `RequestValidationError`.

And it also includes a default exception handler for it.

			if e := enc.Encode(struct {
				Versions []version
			}{Versions: versions}); e != nil {
				return nil, e
			}
			data = b
		default:
			return nil, fmt.Errorf("unknown metadata version %d", minor)
		}

		if datajson {
			b, e := data.json()
			if e != nil {
				return nil, e
			}
			buf = bytes.NewBuffer(b)
		}

		return buf.Bytes(), nil
	}

			<directory>${project.basedir}/plugins</directory>
			<outputDirectory>fess-${project.version}/es/plugins</outputDirectory>
		</fileSet>
		<!-- es/data -->
		<fileSet>
			<directory>src/main/assemblies/files</directory>
			<outputDirectory>fess-${project.version}/es/data</outputDirectory>
			<excludes>
				<exclude>*</exclude>
			</excludes>
			<filtered>false</filtered>
		</fileSet>
	</fileSets>
	<files>

Keep in mind that if you return a response directly instead of using the `Response` parameter, FastAPI will return it directly.

So, you will have to make sure your data is of the correct type. E.g. it is compatible with JSON, if you are returning a `JSONResponse`.

And also that you are not sending any data that should have been filtered by a `response_model`.

///

### More info { #more-info }

/// note | Technical Details

                    context = new byte[8];
                }
            }
            int data = 32;
            if (context != null) {
                data += 8;
            }
            if (targetInformation != null) {
                data += 8;
            }
            final byte[] type2 = new byte[data + target.length + (targetInformation != null ? targetInformation.length : 0)];