Re: Trigger phrases in Github Actions

[Danny McCormick via dev]

I don't think using trigger comments is generally super common, so no. I do
still think it's a useful feature to have though, and part of GHA's
approach is that everything is intentionally extensible and feature light
so that you can tailor it to your org's needs.

Actually, digging in further, it does look like the approach I recommended
might not work out - from
https://github.community/t/on-issue-comment-events-are-not-triggering-workflows/16784/13
it looks like issue_comment always triggers on master unfortunately.

Maybe a ]better approach here would be to use an action like
https://github.com/peter-evans/repository-dispatch to trigger workflows on
issue comment. That would allow us to have a single workflow that reads the
issue comment and triggers a workflow as needed. The only downside is that
it would rely on an external token that would need to be rotated on a
yearly basis. It also puts all the issue triggering logic in a single place
which is nice.


On Thu, Jul 14, 2022 at 5:07 PM Kenneth Knowles  wrote:

> Is this an idiomatic way to trigger GHA?
>
> On Thu, Jul 14, 2022 at 1:36 PM Danny McCormick via dev <
> dev@beam.apache.org> wrote:
>
>> Hey Fer,
>>
>> I'm not 100% sure I follow what you're trying to do, but one approach you
>> could take is to gate everything off of an if like:
>>
>> ` if {{ (github.event.issue.pull_request && github.event.comment && 
>> contains(github.event.comment.body,
>> "PHRASE")) || !github.event.comment }}
>>
>> Basically, that's doing: `if ( &&  &&
>> ) || `
>>
>> I haven't tested it so it might be a little off syntactically, but I
>> believe that should generally do what you're trying to do. FWIW, you might
>> find it helpful to dump the context with an action like this
>>  in a test repo -
>> that will show you exactly what is available in the github context for each
>> kind of event so that you can use them accordingly.
>>
>> Thanks,
>> Danny
>>
>> On Thu, Jul 14, 2022 at 3:20 PM Fer Morales Martinez <
>> fernando.mora...@wizeline.com> wrote:
>>
>>> Hello everyone!
>>>
>>> As part of the migration of the precommit and postcommit jobs from
>>> jenkins over to github actions, we're trying to implement the *trigger
>>> phrase* functionality.
>>> Our first approach was to use issue_comment
>>> 
>>> One problem we noticed after testing is that it looks like issue_comment
>>> is mutually exclusive with the other events. For example, given the
>>> following flow
>>>
>>> name: Java Tests
>>> on:
>>>   schedule:
>>> - cron: '10 2 * * *'
>>>   push:
>>> branches: ['master', 'release-*']
>>>   pull_request:
>>> branches: ['master', 'release-*']
>>> paths: ['sdks/java/**', 'model/**', 'runners/**', 'examples/java/**',
>>> 'examples/kotlin/**', 'release/**', 'buildSrc/**']
>>>   issue_comment:
>>>   types: [created]
>>>
>>> jobs:
>>>   pr_commented:
>>>   # This job only runs for pull request comments
>>>   name: PR comment
>>> if: ${{ github.event.issue.pull_request }}
>>> runs-on: ubuntu-latest
>>> steps:
>>>- run: |
>>>   echo A comment on PR $NUMBER
>>> env:
>>>NUMBER: ${{ github.event.issue.number }}
>>>
>>>   issue_commented:
>>> # This job only runs for issue comments
>>> name: Issue comment
>>> if: ${{ !github.event.issue.pull_request }}
>>> runs-on: ubuntu-latest
>>> steps:
>>>   - run: |
>>>   echo A comment on issue $NUMBER
>>> env:
>>>   NUMBER: ${{ github.event.issue.number }}
>>>
>>> the flow will get kicked off but upon validating the if conditional,
>>> neither job will run since the github.event.issue.pull_request parameter is
>>> not present.
>>>
>>> Another caveat is that we'd have to populate with an if statement every
>>> job we wanted to execute by way of a trigger phrase.
>>>
>>> Does someone have experience with this kind of work? Has someone
>>> implemented trigger phrases in github actions?
>>>
>>> Thanks!
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *This email and its contents (including any attachments) are being sent
>>> toyou on the condition of confidentiality and may be protected by
>>> legalprivilege. Access to this email by anyone other than the intended
>>> recipientis unauthorized. If you are not the intended recipient, please
>>> immediatelynotify the sender by replying to this message and delete the
>>> materialimmediately from your system. Any further use, dissemination,
>>> distributionor reproduction of this email is strictly prohibited. Further,
>>> norepresentation is made with respect to any content contained in this
>>> email.*
>>
>>

Re: Trigger phrases in Github Actions

[Kenneth Knowles]

Is this an idiomatic way to trigger GHA?

On Thu, Jul 14, 2022 at 1:36 PM Danny McCormick via dev 
wrote:

> Hey Fer,
>
> I'm not 100% sure I follow what you're trying to do, but one approach you
> could take is to gate everything off of an if like:
>
> ` if {{ (github.event.issue.pull_request && github.event.comment && 
> contains(github.event.comment.body,
> "PHRASE")) || !github.event.comment }}
>
> Basically, that's doing: `if ( &&  &&
> ) || `
>
> I haven't tested it so it might be a little off syntactically, but I
> believe that should generally do what you're trying to do. FWIW, you might
> find it helpful to dump the context with an action like this
>  in a test repo -
> that will show you exactly what is available in the github context for each
> kind of event so that you can use them accordingly.
>
> Thanks,
> Danny
>
> On Thu, Jul 14, 2022 at 3:20 PM Fer Morales Martinez <
> fernando.mora...@wizeline.com> wrote:
>
>> Hello everyone!
>>
>> As part of the migration of the precommit and postcommit jobs from
>> jenkins over to github actions, we're trying to implement the *trigger
>> phrase* functionality.
>> Our first approach was to use issue_comment
>> 
>> One problem we noticed after testing is that it looks like issue_comment
>> is mutually exclusive with the other events. For example, given the
>> following flow
>>
>> name: Java Tests
>> on:
>>   schedule:
>> - cron: '10 2 * * *'
>>   push:
>> branches: ['master', 'release-*']
>>   pull_request:
>> branches: ['master', 'release-*']
>> paths: ['sdks/java/**', 'model/**', 'runners/**', 'examples/java/**',
>> 'examples/kotlin/**', 'release/**', 'buildSrc/**']
>>   issue_comment:
>>   types: [created]
>>
>> jobs:
>>   pr_commented:
>>   # This job only runs for pull request comments
>>   name: PR comment
>> if: ${{ github.event.issue.pull_request }}
>> runs-on: ubuntu-latest
>> steps:
>>- run: |
>>   echo A comment on PR $NUMBER
>> env:
>>NUMBER: ${{ github.event.issue.number }}
>>
>>   issue_commented:
>> # This job only runs for issue comments
>> name: Issue comment
>> if: ${{ !github.event.issue.pull_request }}
>> runs-on: ubuntu-latest
>> steps:
>>   - run: |
>>   echo A comment on issue $NUMBER
>> env:
>>   NUMBER: ${{ github.event.issue.number }}
>>
>> the flow will get kicked off but upon validating the if conditional,
>> neither job will run since the github.event.issue.pull_request parameter is
>> not present.
>>
>> Another caveat is that we'd have to populate with an if statement every
>> job we wanted to execute by way of a trigger phrase.
>>
>> Does someone have experience with this kind of work? Has someone
>> implemented trigger phrases in github actions?
>>
>> Thanks!
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *This email and its contents (including any attachments) are being sent
>> toyou on the condition of confidentiality and may be protected by
>> legalprivilege. Access to this email by anyone other than the intended
>> recipientis unauthorized. If you are not the intended recipient, please
>> immediatelynotify the sender by replying to this message and delete the
>> materialimmediately from your system. Any further use, dissemination,
>> distributionor reproduction of this email is strictly prohibited. Further,
>> norepresentation is made with respect to any content contained in this
>> email.*
>
>

Re: Trigger phrases in Github Actions

[Danny McCormick via dev]

Hey Fer,

I'm not 100% sure I follow what you're trying to do, but one approach you
could take is to gate everything off of an if like:

` if {{ (github.event.issue.pull_request && github.event.comment &&
contains(github.event.comment.body,
"PHRASE")) || !github.event.comment }}

Basically, that's doing: `if ( &&  && ) || `

I haven't tested it so it might be a little off syntactically, but I
believe that should generally do what you're trying to do. FWIW, you might
find it helpful to dump the context with an action like this
 in a test repo - that
will show you exactly what is available in the github context for each kind
of event so that you can use them accordingly.

Thanks,
Danny

On Thu, Jul 14, 2022 at 3:20 PM Fer Morales Martinez <
fernando.mora...@wizeline.com> wrote:

> Hello everyone!
>
> As part of the migration of the precommit and postcommit jobs from jenkins
> over to github actions, we're trying to implement the *trigger phrase*
> functionality.
> Our first approach was to use issue_comment
> 
> One problem we noticed after testing is that it looks like issue_comment
> is mutually exclusive with the other events. For example, given the
> following flow
>
> name: Java Tests
> on:
>   schedule:
> - cron: '10 2 * * *'
>   push:
> branches: ['master', 'release-*']
>   pull_request:
> branches: ['master', 'release-*']
> paths: ['sdks/java/**', 'model/**', 'runners/**', 'examples/java/**',
> 'examples/kotlin/**', 'release/**', 'buildSrc/**']
>   issue_comment:
>   types: [created]
>
> jobs:
>   pr_commented:
>   # This job only runs for pull request comments
>   name: PR comment
> if: ${{ github.event.issue.pull_request }}
> runs-on: ubuntu-latest
> steps:
>- run: |
>   echo A comment on PR $NUMBER
> env:
>NUMBER: ${{ github.event.issue.number }}
>
>   issue_commented:
> # This job only runs for issue comments
> name: Issue comment
> if: ${{ !github.event.issue.pull_request }}
> runs-on: ubuntu-latest
> steps:
>   - run: |
>   echo A comment on issue $NUMBER
> env:
>   NUMBER: ${{ github.event.issue.number }}
>
> the flow will get kicked off but upon validating the if conditional,
> neither job will run since the github.event.issue.pull_request parameter is
> not present.
>
> Another caveat is that we'd have to populate with an if statement every
> job we wanted to execute by way of a trigger phrase.
>
> Does someone have experience with this kind of work? Has someone
> implemented trigger phrases in github actions?
>
> Thanks!
>
>
>
>
>
>
>
>
>
> *This email and its contents (including any attachments) are being sent
> toyou on the condition of confidentiality and may be protected by
> legalprivilege. Access to this email by anyone other than the intended
> recipientis unauthorized. If you are not the intended recipient, please
> immediatelynotify the sender by replying to this message and delete the
> materialimmediately from your system. Any further use, dissemination,
> distributionor reproduction of this email is strictly prohibited. Further,
> norepresentation is made with respect to any content contained in this
> email.*

Trigger phrases in Github Actions

[Fer Morales Martinez]

Hello everyone!

As part of the migration of the precommit and postcommit jobs from jenkins
over to github actions, we're trying to implement the *trigger phrase*
functionality.
Our first approach was to use issue_comment

One problem we noticed after testing is that it looks like issue_comment is
mutually exclusive with the other events. For example, given the following
flow

name: Java Tests
on:
  schedule:
- cron: '10 2 * * *'
  push:
branches: ['master', 'release-*']
  pull_request:
branches: ['master', 'release-*']
paths: ['sdks/java/**', 'model/**', 'runners/**', 'examples/java/**',
'examples/kotlin/**', 'release/**', 'buildSrc/**']
  issue_comment:
  types: [created]

jobs:
  pr_commented:
  # This job only runs for pull request comments
  name: PR comment
if: ${{ github.event.issue.pull_request }}
runs-on: ubuntu-latest
steps:
   - run: |
  echo A comment on PR $NUMBER
env:
   NUMBER: ${{ github.event.issue.number }}

  issue_commented:
# This job only runs for issue comments
name: Issue comment
if: ${{ !github.event.issue.pull_request }}
runs-on: ubuntu-latest
steps:
  - run: |
  echo A comment on issue $NUMBER
env:
  NUMBER: ${{ github.event.issue.number }}

the flow will get kicked off but upon validating the if conditional,
neither job will run since the github.event.issue.pull_request parameter is
not present.

Another caveat is that we'd have to populate with an if statement every job
we wanted to execute by way of a trigger phrase.

Does someone have experience with this kind of work? Has someone
implemented trigger phrases in github actions?

Thanks!

-- 
*This email and its contents (including any attachments) are being sent to
you on the condition of confidentiality and may be protected by legal
privilege. Access to this email by anyone other than the intended recipient
is unauthorized. If you are not the intended recipient, please immediately
notify the sender by replying to this message and delete the material
immediately from your system. Any further use, dissemination, distribution
or reproduction of this email is strictly prohibited. Further, no
representation is made with respect to any content contained in this email.*

Beam Dependency Check Report (2022-07-14)

[Apache Jenkins Server]

High Priority Dependency Updates Of Beam Python SDK:


  Dependency Name
  Current Version
  Latest Version
  Release Date Of the Current Used Version
  Release Date Of The Latest Release
  
cachetools
4.2.4
5.2.0
2021-12-27
2022-06-02
chromedriver-binary
100.0.4896.60.0
104.0.5112.29.0
2022-05-05
2022-07-14
dill
0.3.1.1
0.3.5.1
2019-10-07
2022-05-26
distlib
0.3.1
0.3.5
2021-05-31
2022-07-14
google-api-core
1.32.0
2.8.2
None
2022-06-16
google-auth
1.35.0
2.9.1
2021-08-23
2022-07-14
google-cloud-bigquery
2.34.4
3.2.0
2022-06-09
2022-06-09
google-cloud-bigtable
1.7.2
2.10.1
2022-06-09
2022-06-16
google-cloud-dataproc
3.1.1
4.0.3
2022-02-21
2022-06-09
google-cloud-datastore
1.15.5
2.7.2
2022-06-16
2022-07-14
google-cloud-language
1.3.2
2.5.1
2022-06-16
2022-07-14
google-cloud-recommendations-ai
0.2.0
0.7.0
2021-07-05
2022-07-14
google-cloud-spanner
1.19.3
3.16.0
2022-06-16
2022-07-14
google-cloud-videointelligence
1.16.3
2.7.1
2022-06-16
2022-06-09
google-cloud-vision
1.0.2
2.7.3
2022-06-16
2022-06-09
grpcio-tools
1.37.0
1.47.0
2021-04-12
2022-06-23
jupyter-client
6.1.12
7.3.4
2021-04-12
2022-06-09
mistune
0.8.4
2.0.3
2021-12-06
2022-06-30
mock
2.0.0
4.0.3
2022-06-02
2020-12-14
mypy-protobuf
1.18
3.2.0
2020-03-24
2022-01-24
Pillow
7.2.0
9.2.0
2020-10-19
2022-07-07
pluggy
0.13.1
1.0.0
2021-08-30
2021-08-30
protobuf
3.20.1
4.21.2
2022-06-02
2022-06-30
pyarrow
7.0.0
8.0.0
2022-02-07
2022-05-12
PyHamcrest
1.10.1
2.0.3
2020-01-20
2021-12-13
pymongo
3.12.3
4.1.1
2021-12-13
2022-04-14
pytest
4.6.11
7.1.2
2020-07-08
2022-05-05
pytest-timeout
1.4.2
2.1.0
2021-10-11
2022-01-24
pytest-xdist
1.34.0
2.5.0
2020-08-17
2021-12-13
selenium
3.141.0
4.3.0
2021-11-18
2022-06-30
setuptools
62.6.0
63.2.0
2022-06-23
2022-07-14
tenacity
5.1.5
8.0.1
2019-11-11
2021-07-19
High Priority Dependency Updates Of Beam Java SDK:


  Dependency Name
  Current Version
  Latest Version
  Release Date Of the Current Used Version
  Release Date Of The Latest Release
  
biz.aQute:bndlib
1.50.0
2.0.0.20130123-133441
2011-11-04
2013-02-27
com.alibaba:fastjson
1.2.69
2.0.9
2020-05-31
2022-07-10
com.amazonaws:amazon-kinesis-client
1.14.2
1.14.8
2021-02-24
2022-02-24
com.amazonaws:amazon-kinesis-producer
0.14.1
0.14.12
2020-07-31
2022-03-16
com.azure:azure-core
1.9.0
1.30.0
2020-10-02
2022-06-30
com.azure:azure-identity
1.0.8
1.5.3
2020-07-07
2022-06-30
com.azure:azure-storage-blob
12.10.0
12.18.0
2021-01-15
2022-07-07
com.azure:azure-storage-common
12.10.0
12.17.0
2021-01-14
2022-07-07
com.clearspring.analytics:stream
2.9.5
2.9.8
2016-08-01
2019-08-27
com.datastax.cassandra:cassandra-driver-core
3.10.2
4.0.0
2020-08-26
2019-03-18
com.datastax.cassandra:cassandra-driver-mapping
3.10.2
3.11.2
2020-08-26
2022-04-28
com.esotericsoftware:kryo
4.0.2
5.3.0
2018-03-20
2022-02-11
com.esotericsoftware.kryo:kryo
2.21
2.24.0
2013-02-27
2014-05-04
com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin
0.33.0
0.42.0
2020-09-14
2022-02-07
com.github.jbellis:jamm
0.3.0
0.3.3
2014-11-19
2018-11-16

Re: Fun with WebAssembly transforms

[Luke Cwik via dev]

Thanks Cham, I wasn't up to speed as to where Xlang was wrt to those
transforms.

On Wed, Jul 13, 2022 at 9:32 PM Chamikara Jayalath 
wrote:

> +1 and this is exactly what I suggested as well. Python Dataframe,
> RunInference, Python Map are available via x-lang for Java already [1] and
> all three need/use simple UDFs to customize operation. There is some logic
> that needs to be added to use Python transforms from Go SDK. As you
> suggested there are many Java x-lang transforms that can use simple UDF
> support as well. Either language combination should work to implement a
> first proof of concept for WASI support while also addressing an existing
> limitation.
>
> Thanks,
> Cham
>
> [1]
> https://github.com/apache/beam/tree/master/sdks/java/extensions/python/src/main/java/org/apache/beam/sdk/extensions/python/transforms
>
> On Wed, Jul 13, 2022 at 8:26 PM Kenneth Knowles  wrote:
>
>> I agree with Luke. Targeting little helper UDFs that go along with IOs
>> are actually a major feature gap for xlang - like timestamp extractors that
>> have to parse particular data formats. This could be a very useful place to
>> try out the design options. I think we can simplify the problem by
>> insisting that they are pure functions that do not access state or side
>> inputs.
>>
>> On Wed, Jul 13, 2022 at 7:52 PM Luke Cwik via dev 
>> wrote:
>>
>>> I think an easier target would be to support things like
>>> DynamicDestinations for Java IO connectors that are exposed as XLang for
>>> Go/Python .
>>>
>>> This is because Go/Python  have good
>>> transpiling support to WebAssembly and we already exposed several Java IO
>>> XLang connectors already so its about plumbing one more thing through for
>>> these IO connectors.
>>>
>>> What interface should we expect for UDFs / UDAFs and should they be
>>> purpose oriented or should we do something like we did for portability
>>> where we have a graph of transforms that we feed arbitrary data in/out
>>> from. The latter would have the benefit of allowing the runner to embed the
>>> language execution directly within the runner and would pay the Wasm
>>> communication tax instead of the gRPC communication tax. If we do the
>>> former we still have the same issues where we have to be able to have a
>>> type system to pass information between the host system and the transpiled
>>> WebAssembly code that wraps the users UDF/UDAF and what if the UDF wants
>>> access to side inputs or user state ...
>>>
>>> On Wed, Jul 13, 2022 at 4:09 PM Chamikara Jayalath 
>>> wrote:
>>>


 On Wed, Jul 13, 2022 at 9:31 AM Luke Cwik  wrote:

> First we'll want to choose whether we want to target Wasm, WASI or
> Wagi.
>

 These terms are defined here
 
 if anybody is confused as I am :)


> WASI adds a lot of simple things like access to a clock, random number
> generator, ... that would expand the scope of what transpiled code can do.
> It is debatable whether we'll want the power to run the transpiled code as
> a microservice. Using UDFs for XLang and UDFs and UDAFs for SQL as our
> expected use cases seem to make WASI the best choice. The issue is in the
> details as there is a hodgepodge of what language runtimes support and 
> what
> are the limits of transpiling from a language to WebAssembly.
>

 Agree that WASI seems like a good target since it gives access to
 additional system resources/tooling.


>
> Assuming WASI then it breaks down to these two aspects:
> 1) Does the host language have a runtime?
> Java: https://github.com/wasmerio/wasmer-java
> Python: https://github.com/wasmerio/wasmer-python
> Go: https://github.com/wasmerio/wasmer-go
>
> 2) How good is compilation from source language to WebAssembly
> ?
> Java (very limited):
> Issues with garbage collection and the need to transpile/replace much
> of the VM's capabilities plus the large standard library that everyone 
> uses
> causes a lot of challenges.
> JWebAssembly can do simple things like basic classes, strings, method
> calls. Should be able to compile trivial lambdas to Wasm. There are other
> choices but to my knowledge all are very limited.
>

 That's unfortunate. But hopefully Java support will be implemented soon
 ?


>
> Python  (quite good):
> Features CPython Emscripten browser CPython Emscripten node Pyodide
> subprocess (fork, exec) no no no
> threads no YES WIP
> file system no (only MEMFS) YES (Node raw FS) YES (IDB, Node, …)
> shared extension modules WIP WIP YES
> PyPI packages no no YES

Beam High Priority Issue Report

[beamactions]

This is your daily summary of Beam's current high priority issues that may need 
attention.

See https://beam.apache.org/contribute/issue-priorities for the meaning and 
expectations around issue priorities.

Unassigned P1 Issues:

https://github.com/apache/beam/issues/22217 Trying to connect to Kerberos 
enabled HDFS cluster from Beam facing issues Want to Read from HDFS file and 
write can someone ping a sample working code  
https://github.com/apache/beam/issues/22188 BigQuery Storage API sink sometimes 
gets stuck outputting to an invalid timestamp
https://github.com/apache/beam/issues/21935 [Bug]: Reject illformed GBK Coders
https://github.com/apache/beam/issues/21794 Dataflow runner creates a new timer 
whenever the output timestamp is change
https://github.com/apache/beam/issues/21713 404s in BigQueryIO don't get output 
to Failed Inserts PCollection
https://github.com/apache/beam/issues/21704 beam_PostCommit_Java_DataflowV2 
failures parent bug
https://github.com/apache/beam/issues/21703 pubsublite.ReadWriteIT failing in 
beam_PostCommit_Java_DataflowV1 and V2
https://github.com/apache/beam/issues/21702 SpannerWriteIT failing in beam 
PostCommit Java V1
https://github.com/apache/beam/issues/21701 beam_PostCommit_Java_DataflowV1 
failing with a variety of flakes and errors
https://github.com/apache/beam/issues/21700 
--dataflowServiceOptions=use_runner_v2 is broken
https://github.com/apache/beam/issues/21696 Flink Tests failure :  
java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.beam.runners.core.construction.SerializablePipelineOptions 
https://github.com/apache/beam/issues/21695 DataflowPipelineResult does not 
raise exception for unsuccessful states.
https://github.com/apache/beam/issues/21694 BigQuery Storage API insert with 
writeResult retry and write to error table
https://github.com/apache/beam/issues/21480 flake: 
FlinkRunnerTest.testEnsureStdoutStdErrIsRestored
https://github.com/apache/beam/issues/21473 PVR_Spark2_Streaming perma-red
https://github.com/apache/beam/issues/21472 Dataflow streaming tests failing 
new AfterSynchronizedProcessingTime test
https://github.com/apache/beam/issues/21471 Flakes: Failed to load cache entry
https://github.com/apache/beam/issues/21470 Test flake: test_split_half_sdf
https://github.com/apache/beam/issues/21469 beam_PostCommit_XVR_Flink flaky: 
Connection refused
https://github.com/apache/beam/issues/21468 
beam_PostCommit_Python_Examples_Dataflow failing
https://github.com/apache/beam/issues/21467 GBK and CoGBK streaming Java load 
tests failing
https://github.com/apache/beam/issues/21465 Kafka commit offset drop data on 
failure for runners that have non-checkpointing shuffle
https://github.com/apache/beam/issues/21463 NPE in Flink Portable 
ValidatesRunner streaming suite
https://github.com/apache/beam/issues/21462 Flake in 
org.apache.beam.sdk.io.mqtt.MqttIOTest.testReadObject: Address already in use
https://github.com/apache/beam/issues/21271 pubsublite.ReadWriteIT flaky in 
beam_PostCommit_Java_DataflowV2  
https://github.com/apache/beam/issues/21270 
org.apache.beam.sdk.transforms.CombineTest$WindowingTests.testWindowedCombineGloballyAsSingletonView
 flaky on Dataflow Runner V2
https://github.com/apache/beam/issues/21268 Race between member variable being 
accessed due to leaking uninitialized state via OutboundObserverFactory
https://github.com/apache/beam/issues/21267 WriteToBigQuery submits a duplicate 
BQ load job if a 503 error code is returned from googleapi
https://github.com/apache/beam/issues/21266 
org.apache.beam.sdk.transforms.ParDoLifecycleTest.testTeardownCalledAfterExceptionInProcessElementStateful
 is flaky in Java ValidatesRunner Flink suite.
https://github.com/apache/beam/issues/21265 
apache_beam.runners.portability.fn_api_runner.translations_test.TranslationsTest.test_run_packable_combine_globally
 'apache_beam.coders.coder_impl._AbstractIterable' object is not reversible
https://github.com/apache/beam/issues/21264 beam_PostCommit_Python36 - 
CrossLanguageSpannerIOTest - flakey failing
https://github.com/apache/beam/issues/21263 (Broken Pipe induced) Bricked 
Dataflow Pipeline 
https://github.com/apache/beam/issues/21262 Python AfterAny, AfterAll do not 
follow spec
https://github.com/apache/beam/issues/21261 
org.apache.beam.runners.dataflow.worker.fn.logging.BeamFnLoggingServiceTest.testMultipleClientsFailingIsHandledGracefullyByServer
 is flaky
https://github.com/apache/beam/issues/21260 Python DirectRunner does not emit 
data at GC time
https://github.com/apache/beam/issues/21257 Either Create or DirectRunner fails 
to produce all elements to the following transform
https://github.com/apache/beam/issues/21123 Multiple jobs running on Flink 
session cluster reuse the persistent Python environment.
https://github.com/apache/beam/issues/21121 
apache_beam.examples.streaming_wordcount_it_test.StreamingWordCountIT.test_streaming_wordcount_it
 flakey
https://github.com/apache/beam/issues/21118