labels.depth=Profundidade
labels.excludedPaths=Caminhos a serem excluídos do rastreamento
labels.excludedUrls=URLs a serem excluídas do rastreamento
labels.excludedDocPaths=Caminhos a serem excluídos da pesquisa
labels.excludedDocUrls=URLs a serem excluídas da pesquisa
labels.hostname=Nome do host
labels.id=ID
labels.includedPaths=Caminhos a serem incluídos no rastreamento
labels.includedUrls=URLs a serem incluídas no rastreamento

				// hostSlice from etcd then we should update with newer
				// domainIPs, we proceed to do that here.
				bucketsToBeUpdated.Add(bucket)
				continue
			}

			// No IPs seem to intersect, this means that bucket exists but has
			// different IP addresses perhaps from a different deployment.
			// bucket names are globally unique in federation at a given

# Online help key for backup.
online.help.name.backup=backup
# Online help key for upgrade.
online.help.name.upgrade=upgrade
# Online help key for search request.
online.help.name.sereq=sereq
# Online help key for access token.
online.help.name.accesstoken=accesstoken
# Online help key for suggest.
online.help.name.suggest=suggest
# Online help key for search log.

                        // Ignore a missing signature for SMB < 3.0, as
                        // - the specification does not clearly require that (it does for SMB3+)
                        // - there seem to be server implementations (known: EMC Isilon) that do not sign the final
                        // response
                        if (negoResp.getSelectedDialect().atLeast(DialectVersion.SMB300) || response.isSigned()) {

# END TF TEST SUITE OPTIONS

# START CROSS-COMPILE CONFIGS
# Set execution platform to Linux x86
# Note: Lot of the "host_" flags such as "host_cpu" and "host_crosstool_top"
# flags seem to be actually used to specify the execution platform details. It
# seems it is this way because these flags are old and predate the distinction
# between host and execution platform.
common:cross_compile_base --config=clang_local

   *
   * <p>This method has no effect (returns {@code this}) when called in GWT: it's unclear whether a
   * precomputed matcher is faster, but it certainly would consume more memory (which doesn't seem
   * like a worthwhile tradeoff in a browser).
   */
  public CharMatcher precomputed() {
    return Platform.precomputeCharMatcher(this);
  }