Skip to content

Commit acba70b

Browse files
cloud-java-botcloud-java-bot
authored
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
1 parent 21cf7c6 commit acba70b

90 files changed

Lines changed: 9219 additions & 3938 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎generation_config.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
gapic_generator_version: 2.44.0
2-
googleapis_commitish: b678386866ca6ee40c84c9043beb70992309343e
2+
googleapis_commitish: 54d659d0ae74f39e92755948b821a1495b3cb3c8
33
libraries_bom_version: 26.44.0
44

55
# 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‎

Lines changed: 64 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -5193,8 +5193,10 @@ public com.google.protobuf.ByteString getDisplayNameBytes() {
51935193
*
51945194
*
51955195
* <pre>
5196-
* Normally, a non-zero exit status causes the Task to fail. This flag allows
5197-
* execution of other Runnables to continue instead.
5196+
* Normally, a runnable that returns a non-zero exit status fails and causes
5197+
* the task to fail. However, you can set this field to `true` to allow the
5198+
* task to continue executing its other runnables even if this runnable
5199+
* fails.
51985200
* </pre>
51995201
*
52005202
* <code>bool ignore_exit_status = 3;</code>
@@ -5212,9 +5214,18 @@ public boolean getIgnoreExitStatus() {
52125214
*
52135215
*
52145216
* <pre>
5215-
* This flag allows a Runnable to continue running in the background while the
5216-
* Task executes subsequent Runnables. This is useful to provide services to
5217-
* other Runnables (or to provide debugging support tools like SSH servers).
5217+
* Normally, a runnable that doesn't exit causes its task to fail. However,
5218+
* you can set this field to `true` to configure a background runnable.
5219+
* Background runnables are allowed continue running in the background while
5220+
* the task executes subsequent runnables. For example, background runnables
5221+
* are useful for providing services to other runnables or providing
5222+
* debugging-support tools like SSH servers.
5223+
*
5224+
* Specifically, background runnables are killed automatically (if they have
5225+
* not already exited) a short time after all foreground runnables have
5226+
* completed. Even though this is likely to result in a non-zero exit status
5227+
* for the background runnable, these automatic kills are not treated as task
5228+
* failures.
52185229
* </pre>
52195230
*
52205231
* <code>bool background = 4;</code>
@@ -6876,8 +6887,10 @@ public Builder setDisplayNameBytes(com.google.protobuf.ByteString value) {
68766887
*
68776888
*
68786889
* <pre>
6879-
* Normally, a non-zero exit status causes the Task to fail. This flag allows
6880-
* execution of other Runnables to continue instead.
6890+
* Normally, a runnable that returns a non-zero exit status fails and causes
6891+
* the task to fail. However, you can set this field to `true` to allow the
6892+
* task to continue executing its other runnables even if this runnable
6893+
* fails.
68816894
* </pre>
68826895
*
68836896
* <code>bool ignore_exit_status = 3;</code>
@@ -6892,8 +6905,10 @@ public boolean getIgnoreExitStatus() {
68926905
*
68936906
*
68946907
* <pre>
6895-
* Normally, a non-zero exit status causes the Task to fail. This flag allows
6896-
* execution of other Runnables to continue instead.
6908+
* Normally, a runnable that returns a non-zero exit status fails and causes
6909+
* the task to fail. However, you can set this field to `true` to allow the
6910+
* task to continue executing its other runnables even if this runnable
6911+
* fails.
68976912
* </pre>
68986913
*
68996914
* <code>bool ignore_exit_status = 3;</code>
@@ -6912,8 +6927,10 @@ public Builder setIgnoreExitStatus(boolean value) {
69126927
*
69136928
*
69146929
* <pre>
6915-
* Normally, a non-zero exit status causes the Task to fail. This flag allows
6916-
* execution of other Runnables to continue instead.
6930+
* Normally, a runnable that returns a non-zero exit status fails and causes
6931+
* the task to fail. However, you can set this field to `true` to allow the
6932+
* task to continue executing its other runnables even if this runnable
6933+
* fails.
69176934
* </pre>
69186935
*
69196936
* <code>bool ignore_exit_status = 3;</code>
@@ -6932,9 +6949,18 @@ public Builder clearIgnoreExitStatus() {
69326949
*
69336950
*
69346951
* <pre>
6935-
* This flag allows a Runnable to continue running in the background while the
6936-
* Task executes subsequent Runnables. This is useful to provide services to
6937-
* other Runnables (or to provide debugging support tools like SSH servers).
6952+
* Normally, a runnable that doesn't exit causes its task to fail. However,
6953+
* you can set this field to `true` to configure a background runnable.
6954+
* Background runnables are allowed continue running in the background while
6955+
* the task executes subsequent runnables. For example, background runnables
6956+
* are useful for providing services to other runnables or providing
6957+
* debugging-support tools like SSH servers.
6958+
*
6959+
* Specifically, background runnables are killed automatically (if they have
6960+
* not already exited) a short time after all foreground runnables have
6961+
* completed. Even though this is likely to result in a non-zero exit status
6962+
* for the background runnable, these automatic kills are not treated as task
6963+
* failures.
69386964
* </pre>
69396965
*
69406966
* <code>bool background = 4;</code>
@@ -6949,9 +6975,18 @@ public boolean getBackground() {
69496975
*
69506976
*
69516977
* <pre>
6952-
* This flag allows a Runnable to continue running in the background while the
6953-
* Task executes subsequent Runnables. This is useful to provide services to
6954-
* other Runnables (or to provide debugging support tools like SSH servers).
6978+
* Normally, a runnable that doesn't exit causes its task to fail. However,
6979+
* you can set this field to `true` to configure a background runnable.
6980+
* Background runnables are allowed continue running in the background while
6981+
* the task executes subsequent runnables. For example, background runnables
6982+
* are useful for providing services to other runnables or providing
6983+
* debugging-support tools like SSH servers.
6984+
*
6985+
* Specifically, background runnables are killed automatically (if they have
6986+
* not already exited) a short time after all foreground runnables have
6987+
* completed. Even though this is likely to result in a non-zero exit status
6988+
* for the background runnable, these automatic kills are not treated as task
6989+
* failures.
69556990
* </pre>
69566991
*
69576992
* <code>bool background = 4;</code>
@@ -6970,9 +7005,18 @@ public Builder setBackground(boolean value) {
69707005
*
69717006
*
69727007
* <pre>
6973-
* This flag allows a Runnable to continue running in the background while the
6974-
* Task executes subsequent Runnables. This is useful to provide services to
6975-
* other Runnables (or to provide debugging support tools like SSH servers).
7008+
* Normally, a runnable that doesn't exit causes its task to fail. However,
7009+
* you can set this field to `true` to configure a background runnable.
7010+
* Background runnables are allowed continue running in the background while
7011+
* the task executes subsequent runnables. For example, background runnables
7012+
* are useful for providing services to other runnables or providing
7013+
* debugging-support tools like SSH servers.
7014+
*
7015+
* Specifically, background runnables are killed automatically (if they have
7016+
* not already exited) a short time after all foreground runnables have
7017+
* completed. Even though this is likely to result in a non-zero exit status
7018+
* for the background runnable, these automatic kills are not treated as task
7019+
* failures.
69767020
* </pre>
69777021
*
69787022
* <code>bool background = 4;</code>

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

Lines changed: 16 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -164,8 +164,10 @@ public interface RunnableOrBuilder
164164
*
165165
*
166166
* <pre>
167-
* Normally, a non-zero exit status causes the Task to fail. This flag allows
168-
* execution of other Runnables to continue instead.
167+
* Normally, a runnable that returns a non-zero exit status fails and causes
168+
* the task to fail. However, you can set this field to `true` to allow the
169+
* task to continue executing its other runnables even if this runnable
170+
* fails.
169171
* </pre>
170172
*
171173
* <code>bool ignore_exit_status = 3;</code>
@@ -178,9 +180,18 @@ public interface RunnableOrBuilder
178180
*
179181
*
180182
* <pre>
181-
* This flag allows a Runnable to continue running in the background while the
182-
* Task executes subsequent Runnables. This is useful to provide services to
183-
* other Runnables (or to provide debugging support tools like SSH servers).
183+
* Normally, a runnable that doesn't exit causes its task to fail. However,
184+
* you can set this field to `true` to configure a background runnable.
185+
* Background runnables are allowed continue running in the background while
186+
* the task executes subsequent runnables. For example, background runnables
187+
* are useful for providing services to other runnables or providing
188+
* debugging-support tools like SSH servers.
189+
*
190+
* Specifically, background runnables are killed automatically (if they have
191+
* not already exited) a short time after all foreground runnables have
192+
* completed. Even though this is likely to result in a non-zero exit status
193+
* for the background runnable, these automatic kills are not treated as task
194+
* failures.
184195
* </pre>
185196
*
186197
* <code>bool background = 4;</code>

0 commit comments

Comments
 (0)