appVersion: RELEASE.2024-12-18T13-15-44Z
    created: "2025-01-02T21:34:25.234658257-08:00"
    description: High Performance Object Storage
    digest: 25fa2740480d1ebc9e64340854a6c42d3a7bc39c2a77378da91b21f144faa9af
    home: https://min.io
    icon: https://min.io/resources/img/logo/MINIO_wordmark.png
    keywords:
    - minio
    - storage
    - object-storage
    - s3
    - cluster
    maintainers:
    - email: ******@****.***

labels.user_configuration=Usuário
labels.user_list_name=Nome
labels.user_password=Senha
labels.user_confirm_password=Senha (confirmar)
labels.user_title_details=Usuário
labels.role_configuration=Função
labels.role_list_name=Nome
labels.role_name=Nome
labels.role_title_details=Função
labels.group_configuration=Grupo
labels.group_list_name=Nome
labels.group_name=Nome
labels.group_title_details=Grupo

common --host_copt=-DGRPC_BAZEL_BUILD
common --action_env=GRPC_BAZEL_RUNTIME=1
common --repo_env=PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=upb
common --action_env=PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=upb
# Some targets have the same py source file, but use different
# configurations via `requires-` tags. This results in an action
# conflict when precompiling. Disable to avoid that problem.

   * expect, but there are some subtleties. First, we do guarantee that, if the output future at
   * index n is done, the output future at index n-1 is also done. (But as usual with futures, some
   * listeners for future n may complete before some for future n-1.) However, it is possible, if
   * one input completes with result X and another later with result Y, for Y to come before X in

			input: []byte(`id,time,num,num2,text
1,2010-01-01T,7867786,4565.908123
2,2017-01-02T03:04Z,-5, 0.765111,Some some
`),
			// Since we are doing offset, no headers are used.
			wantResult: `{"id":"1","time":"2010-01-01T","num":"7867786","num2":"4565.908123"}
{"id":"2","time":"2017-01-02T03:04Z","num":"-5","num2":" 0.765111","text":"Some some"}`,
			wantErr: false,
			requestXML: []byte(`<?xml version="1.0" encoding="UTF-8"?>

		<version>15.6.0-SNAPSHOT</version>
		<relativePath />
	</parent>
	<properties>
		<!-- DEB & RPM build -->
		<packaging.fess.home.dir>/usr/share/fess</packaging.fess.home.dir>
		<packaging.fess.app.dir>${packaging.fess.home.dir}/app</packaging.fess.app.dir>
		<packaging.fess.bin.dir>${packaging.fess.home.dir}/bin</packaging.fess.bin.dir>
		<packaging.fess.conf.dir>/etc/fess</packaging.fess.conf.dir>

    public static final String MULTIMODULE_PROJECT_DIRECTORY = "maven.multiModuleProjectDirectory";

    /**
     * @deprecated Use {@link System#getProperty(String)} with "user.home" instead
     */
    public static final String USER_HOME = System.getProperty("user.home");

    /**
     * @deprecated Use {@link org.apache.maven.api.Constants#MAVEN_USER_CONF} instead
     */

labels.employeeNumber=Employee Number
labels.user_telephoneNumber=Telephone Number
labels.telephoneNumber=Telephone Number
labels.user_homePhone=Home Phone
labels.homePhone=Home Phone
labels.user_homePostalAddress=Home Postal Address
labels.homePostalAddress=Home Postal Address
labels.user_labeledURI=labeledURI
labels.labeledURI=labeledURI
labels.user_roomNumber=Room Number
labels.roomNumber=Room Number

//   materialized in the address space of the calling process.
// * int is used as an index into arrays.
// * Deletion functions are safe to call on nullptr.
//
// Questions left to address:
// * Might at some point need a way for callers to provide their own Env.
// * Maybe add TF_TensorShape that encapsulates dimension info.
//
// Design decisions made:
// * Backing store for tensor memory has an associated deallocation

labels.employeeNumber=Employee Number
labels.user_telephoneNumber=Telephone Number
labels.telephoneNumber=Telephone Number
labels.user_homePhone=Home Phone
labels.homePhone=Home Phone
labels.user_homePostalAddress=Home Postal Address
labels.homePostalAddress=Home Postal Address
labels.user_labeledURI=labeledURI
labels.labeledURI=labeledURI
labels.user_roomNumber=Room Number
labels.roomNumber=Room Number