Re: PreCommit tests not running

[Boyuan Zhang]

There is an infra issue ongoing:
https://issues.apache.org/jira/browse/INFRA-21976, which affects all beam
tests.

On Mon, Jun 7, 2021 at 9:21 PM Reuven Lax  wrote:

> https://github.com/apache/beam/pull/14949
>
> Java PreCommit has been pending for 2 days. Is something wrong
> with Jenkins?
>
> Reuven
>

PreCommit tests not running

[Reuven Lax]

https://github.com/apache/beam/pull/14949

Java PreCommit has been pending for 2 days. Is something wrong with Jenkins?

Reuven

Re: Allyship workshops for open source contributors

[Kenneth Knowles]

Yes please!

On Thu, Jun 3, 2021, 18:32 Ratnakar Malla  wrote:

> +1
>
>
> --
> *From:* Austin Bennett 
> *Sent:* Thursday, June 3, 2021 6:20:25 PM
> *To:* u...@beam.apache.org 
> *Cc:* dev 
> *Subject:* Re: Allyship workshops for open source contributors
>
> +1, assuming timing can work.
>
> On Wed, Jun 2, 2021 at 2:07 PM Aizhamal Nurmamat kyzy 
> wrote:
>
> If we have a good number of people who express interest in this thread, I
> will set up training for the Airflow community.
>
>
> I meant Beam ^^' I am organizing it for the Airflow community as well.
>
>

Re: [VOTE] Release 2.30.0, release candidate #1

[Heejong Lee]

FYI, we now have three binding votes and I will close the vote tomorrow
morning.

The RC build is validated for most quickstart and mobile gaming examples
except Flink / Spark runner on YARN and standalone custers (more details in
the spreadsheet[9] from the original announcement).

On Thu, Jun 3, 2021 at 6:12 PM Robert Bradshaw  wrote:

> +1 (binding)
>
> Verified the signatures are all good and the source tarball matches github.
>
> On Thu, Jun 3, 2021 at 3:38 PM Ahmet Altay  wrote:
> >
> > +1 (binding) - I ran python quickstart examples on the direct runner.
> >
> > Thank you for preparing the RC!
> >
> > Ahmet
> >
> > On Thu, Jun 3, 2021 at 2:58 PM Chamikara Jayalath 
> wrote:
> >>
> >> +1 (binding)
> >>
> >> Tested some Java quickstart validations and multi-language pipelines.
> >>
> >> Thanks,
> >> Cham
> >>
> >> On Thu, Jun 3, 2021 at 2:03 PM Tomo Suzuki  wrote:
> >>>
> >>> +1 (non-binding)
> >>>
> >>> Thank you for the preparation. With the GCP dependencies of my
> interest, the GitHub checks worked.
> >>>
> >>>
> >>>
> >>> On Thu, Jun 3, 2021 at 4:55 AM Heejong Lee  wrote:
> 
>  Hi everyone,
> 
>  Please review and vote on the release candidate #1 for the version
> 2.30.0, as follows:
>  [ ] +1, Approve the release
>  [ ] -1, Do not approve the release (please provide specific comments)
> 
>  Reviewers are encouraged to test their own use cases with the release
> candidate, and vote +1 if no issues are found.
> 
>  The complete staging area is available for your review, which
> includes:
>  * JIRA release notes [1],
>  * the official Apache source release to be deployed to
> dist.apache.org [2], which is signed with the key with fingerprint
> DBC03F1CCF4240FBD0F256F054550BE0F4C0A24D [3],
>  * all artifacts to be deployed to the Maven Central Repository [4],
>  * source code tag "v2.30.0-RC1" [5],
>  * website pull request listing the release [6], publishing the API
> reference manual [7], and the blog post [8].
>  * Java artifacts were built with Maven 3.6.3 and OpenJDK 1.8.0_292.
>  * Python artifacts are deployed along with the source release to the
> dist.apache.org [2].
>  * Validation sheet with a tab for 2.30.0 release to help with
> validation [9].
>  * Docker images published to Docker Hub [10].
>  * Python artifacts are published to pypi as a pre-release version
> [11].
> 
>  The vote will be open for at least 72 hours. It is adopted by
> majority approval, with at least 3 PMC affirmative votes.
> 
>  Thanks,
>  Heejong
> 
>  [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12349978
>  [2] https://dist.apache.org/repos/dist/dev/beam/2.30.0/
>  [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>  [4]
> https://repository.apache.org/content/repositories/orgapachebeam-1174/
>  [5] https://github.com/apache/beam/tree/v2.30.0-RC1
>  [6] https://github.com/apache/beam/pull/14894
>  [7] https://github.com/apache/beam-site/pull/613
>  [8] https://github.com/apache/beam/pull/14895
>  [9]
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=109662250
>  [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>  [11] https://pypi.org/project/apache-beam/2.30.0rc1/
> >>>
> >>>
> >>>
> >>> --
> >>> Regards,
> >>> Tomo
>

Re: RenameFields behaves differently in DirectRunner

[Reuven Lax]

FYI - this should be fixed by https://github.com/apache/beam/pull/14960

On Thu, Jun 3, 2021 at 10:00 AM Reuven Lax  wrote:

> Correct.
>
> On Thu, Jun 3, 2021 at 9:51 AM Kenneth Knowles  wrote:
>
>> I still don't quite grok the details of how this succeeds or fails in
>> different situations. The invalid row succeeds in serialization because the
>> coder is not sensitive to the way in which it is invalid?
>>
>> Kenn
>>
>> On Wed, Jun 2, 2021 at 2:54 PM Brian Hulette  wrote:
>>
>>> > One thing that's been on the back burner for a long time is making
>>> CoderProperties into a CoderTester like Guava's EqualityTester.
>>>
>>> Reuven's point still applies here though. This issue is not due to a bug
>>> in SchemaCoder, it's a problem with the Row we gave SchemaCoder to encode.
>>> I'm assuming a CoderTester would require manually generating inputs right?
>>> These input Rows represent an illegal state that we wouldn't test with.
>>> (That being said I like the idea of a CoderTester in general)
>>>
>>> Brian
>>>
>>> On Wed, Jun 2, 2021 at 12:11 PM Kenneth Knowles  wrote:
>>>
 Mutability checking might catch that.

 I meant to suggest not putting the check in the pipeline, but offering
 a testing discipline that will catch such issues. One thing that's been on
 the back burner for a long time is making CoderProperties into a
 CoderTester like Guava's EqualityTester. Then it can run through all the
 properties without a user setting up test suites. Downside is that the test
 failure signal gets aggregated.

 Kenn

 On Wed, Jun 2, 2021 at 12:09 PM Brian Hulette 
 wrote:

> Could the DirectRunner just do an equality check whenever it does an
> encode/decode? It sounds like it's already effectively performing
> a CoderProperties.coderDecodeEncodeEqual for every element, just omitting
> the equality check.
>
> On Wed, Jun 2, 2021 at 12:04 PM Reuven Lax  wrote:
>
>> There is no bug in the Coder itself, so that wouldn't catch it. We
>> could insert CoderProperties.coderDecodeEncodeEqual in a subsequent 
>> ParDo,
>> but if the Direct runner already does an encode/decode before that ParDo,
>> then that would have fixed the problem before we could see it.
>>
>> On Wed, Jun 2, 2021 at 11:53 AM Kenneth Knowles 
>> wrote:
>>
>>> Would it be caught by CoderProperties?
>>>
>>> Kenn
>>>
>>> On Wed, Jun 2, 2021 at 8:16 AM Reuven Lax  wrote:
>>>
 I don't think this bug is schema specific - we created a Java
 object that is inconsistent with its encoded form, which could happen 
 to
 any transform.

 This does seem to be a gap in DirectRunner testing though. It also
 makes it hard to test using PAssert, as I believe that puts everything 
 in a
 side input, forcing an encoding/decoding.

 On Wed, Jun 2, 2021 at 8:12 AM Brian Hulette 
 wrote:

> +dev 
>
> > I bet the DirectRunner is encoding and decoding in between,
> which fixes the object.
>
> Do we need better testing of schema-aware (and potentially other
> built-in) transforms in the face of fusion to root out issues like 
> this?
>
> Brian
>
> On Wed, Jun 2, 2021 at 5:13 AM Matthew Ouyang <
> matthew.ouy...@gmail.com> wrote:
>
>> I have some other work-related things I need to do this week, so
>> I will likely report back on this over the weekend.  Thank you for 
>> the
>> explanation.  It makes perfect sense now.
>>
>> On Tue, Jun 1, 2021 at 11:18 PM Reuven Lax 
>> wrote:
>>
>>> Some more context - the problem is that RenameFields outputs (in
>>> this case) Java Row objects that are inconsistent with the actual 
>>> schema.
>>> For example if you have the following schema:
>>>
>>> Row {
>>>field1: Row {
>>>   field2: string
>>> }
>>> }
>>>
>>> And rename field1.field2 -> renamed, you'll get the following
>>> schema
>>>
>>> Row {
>>>   field1: Row {
>>>  renamed: string
>>>}
>>> }
>>>
>>> However the Java object for the _nested_ row will return the old
>>> schema if getSchema() is called on it. This is because we only 
>>> update the
>>> schema on the top-level row.
>>>
>>> I think this explains why your test works in the direct runner.
>>> If the row ever goes through an encode/decode path, it will come 
>>> back
>>> correct. The original incorrect Java objects are no longer around, 
>>> and new
>>> (consistent) objects are constructed from the raw data and the 
>>> PCollection

Re: [PROPOSAL] Preparing for Beam 2.31.0 release

[Andrew Pilloud]

The 2.31.0 release branch was cut based on the last commit on June 2nd and
is now available for cherry-picks[1]. There are currently 3 open release
blocking issues[2].

Andrew

[1] https://github.com/apache/beam/commits/release-2.31.0
[2]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20resolution%20is%20EMPTY%20AND%20fixVersion%20%3D%202.31.0

On Wed, May 26, 2021 at 11:12 AM Ahmet Altay  wrote:

> +1. Thank you Andrew.
>
> On Thu, May 20, 2021 at 1:15 PM Andrew Pilloud 
> wrote:
>
>> Hi All,
>>
>> Beam 2.31.0 release is scheduled to be cut in two weeks, on June 2
>> according to the release calendar [1].
>>
>> I'd like to volunteer myself to be the release manager for this release.
>> I plan on cutting the release branch on the scheduled date. That week
>> starts with a US holiday and I will be on vacation the entire week so I
>> don't expect to make any progress on the release until June 7th. If there
>> is a desire I could delay the release cut by a few days.
>>
>> Any comments or objections?
>>
>> Andrew
>>
>> [1]
>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles
>>
>

Re:

[Pablo Estrada]

+Reuven Lax  do you know if this is already supported or
not?
I have been able to use `JdbcIO.write()` without specifying a statement nor
a statement preparer. Is that not what's necessary? I've done this with a
named class with schemas (i.e. not Row) - is this perhaps the difference?
Best
-P.

On Fri, Jun 4, 2021 at 3:44 PM Robert Bradshaw  wrote:

> That would be great! I don't know much about this particular issue,
> but tips for getting started in general can be found at
> https://beam.apache.org/contribute/
>
> On Thu, Jun 3, 2021 at 10:55 AM Raphael Sanamyan
>  wrote:
> >
> > Hi, community,
> >
> > I would like to start work on this task  beam-10396, I hope nobody minds?
> > Also, if anyone has any details or developments on this task, I would be
> glad if you could share them.
> >
> > Thank you,
> > Raphael.
> >
> >
>

Re: DynamicDestination for AvroIO

[Reuven Lax]

I believe you can do this today using DynamicAvroDestinations

On Mon, Jun 7, 2021 at 11:50 AM Anant Damle  wrote:

> Hi Team,
> I am working on a solution with Beam's Java SD, that requires:
>
>
>1. Read AVRO files using AvroIO.parseGenericRecords
>2. Modify the records (encrypt some attributes) and generate an
>updated Schema
>3. Write the modified record with updated Schema
>
> I'm facing challenges in Step#3, as AvroIO doesn't have an option to read
> Schema from a PCollectionView. I found that BigQueryIO.withSchemaFromView
> 
>  allows
> one to provide Schema through a view.
>
> What should be done for something like AvroIO.withSchemaFromView.
> I'm looking for some guidance on how to achieve this. I would be happy to
> build and contribute it into the Beam.
>
> Thanks,
> Anant
>
>

DynamicDestination for AvroIO

[Anant Damle]

Hi Team,
I am working on a solution with Beam's Java SD, that requires:


   1. Read AVRO files using AvroIO.parseGenericRecords
   2. Modify the records (encrypt some attributes) and generate an updated
   Schema
   3. Write the modified record with updated Schema

I'm facing challenges in Step#3, as AvroIO doesn't have an option to read
Schema from a PCollectionView. I found that BigQueryIO.withSchemaFromView

allows
one to provide Schema through a view.

What should be done for something like AvroIO.withSchemaFromView.
I'm looking for some guidance on how to achieve this. I would be happy to
build and contribute it into the Beam.

Thanks,
Anant

Flaky test issue report (37)

[Beam Jira Bot]

This is your daily summary of Beam's current flaky tests 
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20labels%20%3D%20flake)

These are P1 issues because they have a major negative impact on the community 
and make it hard to determine the quality of the software.

https://issues.apache.org/jira/browse/BEAM-12322: 
FnApiRunnerTestWithGrpcAndMultiWorkers flaky (py precommit) (created 2021-05-10)
https://issues.apache.org/jira/browse/BEAM-12309: 
PubSubIntegrationTest.test_streaming_data_only flake (created 2021-05-07)
https://issues.apache.org/jira/browse/BEAM-12307: 
PubSubBigQueryIT.test_file_loads flake (created 2021-05-07)
https://issues.apache.org/jira/browse/BEAM-12303: Flake in 
PubSubIntegrationTest.test_streaming_with_attributes (created 2021-05-06)
https://issues.apache.org/jira/browse/BEAM-12291: 
org.apache.beam.runners.flink.ReadSourcePortableTest.testExecution[streaming: 
false] is flaky (created 2021-05-05)
https://issues.apache.org/jira/browse/BEAM-12200: 
SamzaStoreStateInternalsTest is flaky (created 2021-04-20)
https://issues.apache.org/jira/browse/BEAM-12163: Python GHA PreCommits 
flake with grpc.FutureTimeoutError on SDK harness startup (created 2021-04-13)
https://issues.apache.org/jira/browse/BEAM-12061: beam_PostCommit_SQL 
failing on KafkaTableProviderIT.testFakeNested (created 2021-03-27)
https://issues.apache.org/jira/browse/BEAM-12019: 
apache_beam.runners.portability.flink_runner_test.FlinkRunnerTestOptimized.test_flink_metrics
 is flaky (created 2021-03-18)
https://issues.apache.org/jira/browse/BEAM-11792: Python precommit failed 
(flaked?) installing package  (created 2021-02-10)
https://issues.apache.org/jira/browse/BEAM-11666: 
apache_beam.runners.interactive.recording_manager_test.RecordingManagerTest.test_basic_execution
 is flaky (created 2021-01-20)
https://issues.apache.org/jira/browse/BEAM-11661: hdfsIntegrationTest 
flake: network not found (py38 postcommit) (created 2021-01-19)
https://issues.apache.org/jira/browse/BEAM-11645: beam_PostCommit_XVR_Flink 
failing (created 2021-01-15)
https://issues.apache.org/jira/browse/BEAM-11541: 
testTeardownCalledAfterExceptionInProcessElement flakes on direct runner. 
(created 2020-12-30)
https://issues.apache.org/jira/browse/BEAM-11540: Linter sometimes flakes 
on apache_beam.dataframe.frames_test (created 2020-12-30)
https://issues.apache.org/jira/browse/BEAM-10995: Java + Universal Local 
Runner: WindowingTest.testWindowPreservation fails (created 2020-09-30)
https://issues.apache.org/jira/browse/BEAM-10987: 
stager_test.py::StagerTest::test_with_main_session flaky on windows py3.6,3.7 
(created 2020-09-29)
https://issues.apache.org/jira/browse/BEAM-10968: flaky test: 
org.apache.beam.sdk.metrics.MetricsTest$AttemptedMetricTests.testAttemptedDistributionMetrics
 (created 2020-09-25)
https://issues.apache.org/jira/browse/BEAM-10955: Flink Java Runner test 
flake: Could not find Flink job  (created 2020-09-23)
https://issues.apache.org/jira/browse/BEAM-10866: 
PortableRunnerTestWithSubprocesses.test_register_finalizations flaky on macOS 
(created 2020-09-09)
https://issues.apache.org/jira/browse/BEAM-10501: 
CheckGrafanaStalenessAlerts and PingGrafanaHttpApi fail with Connection refused 
(created 2020-07-15)
https://issues.apache.org/jira/browse/BEAM-10485: Failure / flake: 
ElasticsearchIOTest > testWriteWithIndexFn (created 2020-07-14)
https://issues.apache.org/jira/browse/BEAM-9649: 
beam_python_mongoio_load_test started failing due to mismatched results 
(created 2020-03-31)
https://issues.apache.org/jira/browse/BEAM-9392: TestStream tests are all 
flaky (created 2020-02-27)
https://issues.apache.org/jira/browse/BEAM-9232: 
BigQueryWriteIntegrationTests is flaky coercing to Unicode (created 2020-01-31)
https://issues.apache.org/jira/browse/BEAM-9119: 
apache_beam.runners.portability.fn_api_runner_test.FnApiRunnerTest[...].test_large_elements
 is flaky (created 2020-01-14)
https://issues.apache.org/jira/browse/BEAM-8101: Flakes in 
ParDoLifecycleTest.testTeardownCalledAfterExceptionInStartBundleStateful for 
Direct, Spark, Flink (created 2019-08-27)
https://issues.apache.org/jira/browse/BEAM-8035: 
[beam_PreCommit_Java_Phrase] [WatchTest.testMultiplePollsWithManyResults]  
Flake: Outputs must be in timestamp order (created 2019-08-22)
https://issues.apache.org/jira/browse/BEAM-7992: Unhandled type_constraint 
in 
apache_beam.io.gcp.bigquery_write_it_test.BigQueryWriteIntegrationTests.test_big_query_write_new_types
 (created 2019-08-16)
https://issues.apache.org/jira/browse/BEAM-7827: 
MetricsTest$AttemptedMetricTests.testAllAttemptedMetrics is flaky on 
DirectRunner (created 2019-07-26)
https://issues.apache.org/jira/browse/BEAM-7752: Java Validates 
DirectRunner: testTeardownCalledAfterExceptionInFinishBundleStateful flaky 
(created 

P1 issues report (41)

[Beam Jira Bot]

This is your daily summary of Beam's current P1 issues, not including flaky 
tests 
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20priority%20%3D%20P1%20AND%20(labels%20is%20EMPTY%20OR%20labels%20!%3D%20flake).

See https://beam.apache.org/contribute/jira-priorities/#p1-critical for the 
meaning and expectations around P1 issues.

https://issues.apache.org/jira/browse/BEAM-12443: No Information of failed 
Query in JdbcIO (created 2021-06-02)
https://issues.apache.org/jira/browse/BEAM-12440: Wrong version string for 
legacy Dataflow Java container (created 2021-06-01)
https://issues.apache.org/jira/browse/BEAM-12436: 
[beam_PostCommit_Go_VR_flink| beam_PostCommit_Go_VR_spark] 
[:sdks:go:test:flinkValidatesRunner] Failure summary (created 2021-06-01)
https://issues.apache.org/jira/browse/BEAM-12422: Vendored gRPC 1.36.0 is 
using a log4j version with security issues (created 2021-05-28)
https://issues.apache.org/jira/browse/BEAM-12416: Python Kafka transforms 
are failing due to "No Runner was specified" (created 2021-05-27)
https://issues.apache.org/jira/browse/BEAM-12396: 
beam_PostCommit_XVR_Direct failed (flaked?) (created 2021-05-24)
https://issues.apache.org/jira/browse/BEAM-12389: 
beam_PostCommit_XVR_Dataflow flaky: Expand method not found (created 2021-05-21)
https://issues.apache.org/jira/browse/BEAM-12387: beam_PostCommit_Python* 
timing out (created 2021-05-21)
https://issues.apache.org/jira/browse/BEAM-12386: 
beam_PostCommit_Py_VR_Dataflow(_V2) failing metrics tests (created 2021-05-21)
https://issues.apache.org/jira/browse/BEAM-12380: Go SDK Kafka IO Transform 
implemented via XLang (created 2021-05-21)
https://issues.apache.org/jira/browse/BEAM-12374: Spark postcommit failing 
ResumeFromCheckpointStreamingTest (created 2021-05-20)
https://issues.apache.org/jira/browse/BEAM-12337: Replace invalid UW 
container name for Java SDK (created 2021-05-14)
https://issues.apache.org/jira/browse/BEAM-12320: 
PubsubTableProviderIT.testSQLSelectsArrayAttributes[0] failing in SQL 
PostCommit (created 2021-05-10)
https://issues.apache.org/jira/browse/BEAM-12310: 
beam_PostCommit_Java_DataflowV2 failing (created 2021-05-07)
https://issues.apache.org/jira/browse/BEAM-12279: Implement 
destination-dependent sharding in FileIO.writeDynamic (created 2021-05-04)
https://issues.apache.org/jira/browse/BEAM-12256: 
PubsubIO.readAvroGenericRecord creates SchemaCoder that fails to decode some 
Avro logical types (created 2021-04-29)
https://issues.apache.org/jira/browse/BEAM-11959: Python Beam SDK Harness 
hangs when installing pip packages (created 2021-03-11)
https://issues.apache.org/jira/browse/BEAM-11906: No trigger early 
repeatedly for session windows (created 2021-03-01)
https://issues.apache.org/jira/browse/BEAM-11875: XmlIO.Read does not 
handle XML encoding per spec (created 2021-02-26)
https://issues.apache.org/jira/browse/BEAM-11828: JmsIO is not 
acknowledging messages correctly (created 2021-02-17)
https://issues.apache.org/jira/browse/BEAM-11755: Cross-language 
consistency (RequiresStableInputs) is quietly broken (at least on portable 
flink runner) (created 2021-02-05)
https://issues.apache.org/jira/browse/BEAM-11578: `dataflow_metrics` 
(python) fails with TypeError (when int overflowing?) (created 2021-01-06)
https://issues.apache.org/jira/browse/BEAM-11434: Expose Spanner 
admin/batch clients in Spanner Accessor (created 2020-12-10)
https://issues.apache.org/jira/browse/BEAM-11148: Kafka 
commitOffsetsInFinalize OOM on Flink (created 2020-10-28)
https://issues.apache.org/jira/browse/BEAM-11017: Timer with dataflow 
runner can be set multiple times (dataflow runner) (created 2020-10-05)
https://issues.apache.org/jira/browse/BEAM-10670: Make non-portable 
Splittable DoFn the only option when executing Java "Read" transforms (created 
2020-08-10)
https://issues.apache.org/jira/browse/BEAM-10617: python 
CombineGlobally().with_fanout() cause duplicate combine results for sliding 
windows (created 2020-07-31)
https://issues.apache.org/jira/browse/BEAM-10569: SpannerIO tests don't 
actually assert anything. (created 2020-07-23)
https://issues.apache.org/jira/browse/BEAM-10288: Quickstart documents are 
out of date (created 2020-06-19)
https://issues.apache.org/jira/browse/BEAM-10244: Populate requirements 
cache fails on poetry-based packages (created 2020-06-11)
https://issues.apache.org/jira/browse/BEAM-10100: FileIO writeDynamic with 
AvroIO.sink not writing all data (created 2020-05-27)
https://issues.apache.org/jira/browse/BEAM-9564: Remove insecure ssl 
options from MongoDBIO (created 2020-03-20)
https://issues.apache.org/jira/browse/BEAM-9455: Environment-sensitive 
provisioning for Dataflow (created 2020-03-05)
https://issues.apache.org/jira/browse/BEAM-9293: Python direct runner 
doesn't emit empty 

Re: Jira access

[Alexey Romanenko]

Done.
Welcome to Beam!

—
Alexey

> On 5 Jun 2021, at 03:52, Yu Zhang  wrote:
> 
> Hi Beam Community,
>  
> I’d like to contribute to Beam. Could someone grant me Jira contribution 
> rights?
> My username is yzhang559
>  
> Thanks,
> Yu