chore: Update generation configuration at Wed Aug 21 02:16:07 UTC 2024 (#11088)

* chore: Update generation configuration at Wed Aug 21 02:16:07 UTC 2024 * chore: generate libraries at Wed Aug 21 02:19:34 UTC 2024

Author: cloud-java-bot

generation_config.yaml

@@ -1,5 +1,5 @@
 gapic_generator_version: 2.44.0
-googleapis_commitish: b678386866ca6ee40c84c9043beb70992309343e
+googleapis_commitish: 54d659d0ae74f39e92755948b821a1495b3cb3c8
 libraries_bom_version: 26.44.0
 
 # the libraries are ordered with respect to library name, which is

java-batch/proto-google-cloud-batch-v1/src/main/java/com/google/cloud/batch/v1/Runnable.java

@@ -5193,8 +5193,10 @@ public com.google.protobuf.ByteString getDisplayNameBytes() {
  *
  *
  * <pre>
- * Normally, a non-zero exit status causes the Task to fail. This flag allows
- * execution of other Runnables to continue instead.
+ * Normally, a runnable that returns a non-zero exit status fails and causes
+ * the task to fail. However, you can set this field to `true` to allow the
+ * task to continue executing its other runnables even if this runnable
+ * fails.
  * </pre>
  *
  * <code>bool ignore_exit_status = 3;</code>
@@ -5212,9 +5214,18 @@ public boolean getIgnoreExitStatus() {
  *
  *
  * <pre>
- * This flag allows a Runnable to continue running in the background while the
- * Task executes subsequent Runnables. This is useful to provide services to
- * other Runnables (or to provide debugging support tools like SSH servers).
+ * Normally, a runnable that doesn't exit causes its task to fail. However,
+ * you can set this field to `true` to configure a background runnable.
+ * Background runnables are allowed continue running in the background while
+ * the task executes subsequent runnables. For example, background runnables
+ * are useful for providing services to other runnables or providing
+ * debugging-support tools like SSH servers.
+ *
+ * Specifically, background runnables are killed automatically (if they have
+ * not already exited) a short time after all foreground runnables have
+ * completed. Even though this is likely to result in a non-zero exit status
+ * for the background runnable, these automatic kills are not treated as task
+ * failures.
  * </pre>
  *
  * <code>bool background = 4;</code>
@@ -6876,8 +6887,10 @@ public Builder setDisplayNameBytes(com.google.protobuf.ByteString value) {
  *
  *
  * <pre>
- * Normally, a non-zero exit status causes the Task to fail. This flag allows
- * execution of other Runnables to continue instead.
+ * Normally, a runnable that returns a non-zero exit status fails and causes
+ * the task to fail. However, you can set this field to `true` to allow the
+ * task to continue executing its other runnables even if this runnable
+ * fails.
  * </pre>
  *
  * <code>bool ignore_exit_status = 3;</code>
@@ -6892,8 +6905,10 @@ public boolean getIgnoreExitStatus() {
  *
  *
  * <pre>
- * Normally, a non-zero exit status causes the Task to fail. This flag allows
- * execution of other Runnables to continue instead.
+ * Normally, a runnable that returns a non-zero exit status fails and causes
+ * the task to fail. However, you can set this field to `true` to allow the
+ * task to continue executing its other runnables even if this runnable
+ * fails.
  * </pre>
  *
  * <code>bool ignore_exit_status = 3;</code>
@@ -6912,8 +6927,10 @@ public Builder setIgnoreExitStatus(boolean value) {
  *
  *
  * <pre>
- * Normally, a non-zero exit status causes the Task to fail. This flag allows
- * execution of other Runnables to continue instead.
+ * Normally, a runnable that returns a non-zero exit status fails and causes
+ * the task to fail. However, you can set this field to `true` to allow the
+ * task to continue executing its other runnables even if this runnable
+ * fails.
  * </pre>
  *
  * <code>bool ignore_exit_status = 3;</code>
@@ -6932,9 +6949,18 @@ public Builder clearIgnoreExitStatus() {
  *
  *
  * <pre>
- * This flag allows a Runnable to continue running in the background while the
- * Task executes subsequent Runnables. This is useful to provide services to
- * other Runnables (or to provide debugging support tools like SSH servers).
+ * Normally, a runnable that doesn't exit causes its task to fail. However,
+ * you can set this field to `true` to configure a background runnable.
+ * Background runnables are allowed continue running in the background while
+ * the task executes subsequent runnables. For example, background runnables
+ * are useful for providing services to other runnables or providing
+ * debugging-support tools like SSH servers.
+ *
+ * Specifically, background runnables are killed automatically (if they have
+ * not already exited) a short time after all foreground runnables have
+ * completed. Even though this is likely to result in a non-zero exit status
+ * for the background runnable, these automatic kills are not treated as task
+ * failures.
  * </pre>
  *
  * <code>bool background = 4;</code>
@@ -6949,9 +6975,18 @@ public boolean getBackground() {
  *
  *
  * <pre>
- * This flag allows a Runnable to continue running in the background while the
- * Task executes subsequent Runnables. This is useful to provide services to
- * other Runnables (or to provide debugging support tools like SSH servers).
+ * Normally, a runnable that doesn't exit causes its task to fail. However,
+ * you can set this field to `true` to configure a background runnable.
+ * Background runnables are allowed continue running in the background while
+ * the task executes subsequent runnables. For example, background runnables
+ * are useful for providing services to other runnables or providing
+ * debugging-support tools like SSH servers.
+ *
+ * Specifically, background runnables are killed automatically (if they have
+ * not already exited) a short time after all foreground runnables have
+ * completed. Even though this is likely to result in a non-zero exit status
+ * for the background runnable, these automatic kills are not treated as task
+ * failures.
  * </pre>
  *
  * <code>bool background = 4;</code>
@@ -6970,9 +7005,18 @@ public Builder setBackground(boolean value) {
  *
  *
  * <pre>
- * This flag allows a Runnable to continue running in the background while the
- * Task executes subsequent Runnables. This is useful to provide services to
- * other Runnables (or to provide debugging support tools like SSH servers).
+ * Normally, a runnable that doesn't exit causes its task to fail. However,
+ * you can set this field to `true` to configure a background runnable.
+ * Background runnables are allowed continue running in the background while
+ * the task executes subsequent runnables. For example, background runnables
+ * are useful for providing services to other runnables or providing
+ * debugging-support tools like SSH servers.
+ *
+ * Specifically, background runnables are killed automatically (if they have
+ * not already exited) a short time after all foreground runnables have
+ * completed. Even though this is likely to result in a non-zero exit status
+ * for the background runnable, these automatic kills are not treated as task
+ * failures.
  * </pre>
  *
  * <code>bool background = 4;</code>

java-batch/proto-google-cloud-batch-v1/src/main/java/com/google/cloud/batch/v1/RunnableOrBuilder.java

@@ -164,8 +164,10 @@ public interface RunnableOrBuilder
  *
  *
  * <pre>
- * Normally, a non-zero exit status causes the Task to fail. This flag allows
- * execution of other Runnables to continue instead.
+ * Normally, a runnable that returns a non-zero exit status fails and causes
+ * the task to fail. However, you can set this field to `true` to allow the
+ * task to continue executing its other runnables even if this runnable
+ * fails.
  * </pre>
  *
  * <code>bool ignore_exit_status = 3;</code>
@@ -178,9 +180,18 @@ public interface RunnableOrBuilder
  *
  *
  * <pre>
- * This flag allows a Runnable to continue running in the background while the
- * Task executes subsequent Runnables. This is useful to provide services to
- * other Runnables (or to provide debugging support tools like SSH servers).
+ * Normally, a runnable that doesn't exit causes its task to fail. However,
+ * you can set this field to `true` to configure a background runnable.
+ * Background runnables are allowed continue running in the background while
+ * the task executes subsequent runnables. For example, background runnables
+ * are useful for providing services to other runnables or providing
+ * debugging-support tools like SSH servers.
+ *
+ * Specifically, background runnables are killed automatically (if they have
+ * not already exited) a short time after all foreground runnables have
+ * completed. Even though this is likely to result in a non-zero exit status
+ * for the background runnable, these automatic kills are not treated as task
+ * failures.
  * </pre>
  *
  * <code>bool background = 4;</code>