# Don't trigger --config=<host platform> when cross-compiling.
build:android --noenable_platform_specific_config
build:ios --noenable_platform_specific_config

# Suppress all C++ compiler warnings, otherwise build logs become 10s of MBs.
build:android --copt=-w
build:ios --copt=-w
build:linux --host_copt=-w
build:macos --copt=-w
build:windows --copt=/W0
build:windows --host_copt=/W0

      <span style="background-color:#007166"><font color="#D3D7CF"> tip </font></span>  Running in development mode, for production use:
             <b>fastapi run</b>

             Logs:

     <span style="background-color:#007166"><font color="#D3D7CF"> INFO </font></span>  Will watch for changes in these directories:
             <b>[</b><font color="#4E9A06">&apos;/home/user/code/awesomeapp&apos;</font><b>]</b>

    /** The key of the message: Delete old search logs */
    public static final String LABELS_purge_search_log_day = "{labels.purge_search_log_day}";

    /** The key of the message: Delete old job logs */
    public static final String LABELS_purge_job_log_day = "{labels.purge_job_log_day}";

    /** The key of the message: Delete old user logs */

       * handleOneInputDone.
       */
      decrementCountAndMaybeComplete(null);
    }
  }

  /**
   * Fails this future with the given Throwable if {@link #allMustSucceed} is true. Also, logs the
   * throwable if it is an {@link Error} or if {@link #allMustSucceed} is {@code true}, the
   * throwable did not cause this future to fail, and it is the first time we've seen that
   * particular Throwable.
   */

    requests with the same POST data get the same cache entry.

 *  New: `HttpLoggingInterceptor.redactQueryParams()` configures the query parameters to redact
    in logs. For best security, don't put sensitive information in query parameters.

 *  New: `ConnectionPool.setPolicy()` configures a minimum connection pool size for a target
    address. Use this to proactively open HTTP connections.

success.upload_bad_word = Uploaded a bad word file.
success.upload_mapping_file = Uploaded a mapping file.
success.send_testmail=Sent a test mail.
success.job_log_delete_all=Deleted job logs.
success.changed_password=Changed your password.
success.started_data_update=Started a data update process.
success.reindex_started=Started re-indexing.
success.bulk_process_started=Started a bulk process.

success.upload_bad_word = Uploaded a bad word file.
success.upload_mapping_file = Uploaded a mapping file.
success.send_testmail=Sent a test mail.
success.job_log_delete_all=Deleted job logs.
success.changed_password=Changed your password.
success.started_data_update=Started a data update process.
success.reindex_started=Started re-indexing.
success.bulk_process_started=Started a bulk process.

     */
    String getGuestUsername();

    /**
     * Property {@code jcifs.smb.client.allowGuestFallback}, defaults to false
     *
     * @return whether to permit guest logins when user authentication is requested
     */
    boolean isAllowGuestFallback();

    /**
     * Property {@code jcifs.smb.client.useDurableHandles}, defaults to true
     *

    /** Request attribute key for storing highlight queries. */
    public static final String HIGHLIGHT_QUERIES = "fess.HighlightQueries";

    /** Request attribute key for storing field logs. */
    public static final String FIELD_LOGS = "fess.FieldLogs";

    // ============================================================
    // Date/Time Format Constants

warning texts were not always using the right format for a command (`add_dir_header` instead of `add-dir-header`). Fixing this included cleaning up flag handling in component-base/logs: that package no longer adds flags to the global flag sets. Commands which want the klog and `--log-flush-frequency` flags must explicitly call `logs.AddFlags`; the new `cli.Run` does that for commands. That helper function also covers flag normalization and printing of usage and errors in a consistent way (print usage text...