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

[Alexey Romanenko]

Just for reference: it looks that it happens only with default package classes 
[1].

[1] https://github.com/raphw/byte-buddy/issues/1301#issuecomment-1218475514


> On 18 Aug 2022, at 12:40, Alexey Romanenko  wrote:
> 
> 
>> On 17 Aug 2022, at 22:52, Kenneth Knowles > > wrote:
>> 
>> Seems like there has been a lot of progress on 
>> https://github.com/raphw/byte-buddy/issues/1301 
>> . Since it has been 
>> identified, I think we can be pretty confident that the version downgrade is 
>> the necessary part. So we can revert the PR for the release, then on main 
>> branch we can proceed with unvendoring but keeping the same version.
> 
> +1 for this.
> 
>> BTW just noting for the thread that I also checked mvn dependency:tree of 
>> Talend/beam-samples and confirmed that only Beam depends on bytebuddy so it 
>> is not a dependency conflict.
> 
> Sorry, I forgot to mention that I'd checked this before I posted that issue 
> on dev@ (to make sure that it depends only on one version of byte_buddy).
> Thanks for highlighting this.
> 
>> I also googled the error message and found 
>> https://stackoverflow.com/questions/51650074/apache-beam-invisible-parameter-type-exception
>>  
>> 
>>  and https://issues.apache.org/jira/browse/BEAM-5061 
>>  where using JDK 10 instead 
>> of 8 causes a similar symptom but it does not seem related. It was never 
>> directly addressed.
> 
> For me, it looks not very related since it’s about pretty old version of 
> byte_buddy and in “beam-samples” we test a build with OpenJDK v8, v11, and 
> even v17 and it fails in the same way for all of them.
> 
> —
> Alexey
> 
>> 
>> Kenn
>> 
>> On Wed, Aug 17, 2022 at 10:36 AM Kiley Sok > > wrote:
>> PR to revert the change for the release 
>> https://github.com/apache/beam/pull/22759 
>> 
>> 
>> I'll rebuild a new RC once the tests pass and the PR is merged.
>> 
>> On Wed, Aug 17, 2022 at 8:16 AM Liam Miller-Cushon > > wrote:
>> On Tue, Aug 16, 2022 at 2:42 PM Kiley Sok > > wrote:
>> Liam, are we okay to roll back this change for this release?
>> 
>> No concerns from me with rolling back to unblock the release.
>> 
>> It looks like this is a change between bytebuddy 1.12.3 and 1.12.4. I filed 
>> https://github.com/raphw/byte-buddy/issues/1301 
>>  to get help understanding 
>> what changed, it sounds like the change might be WAI but there's a suggested 
>> fix. I will prepare a PR for that as a follow-up.
> 

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

[Alexey Romanenko]

> On 17 Aug 2022, at 22:52, Kenneth Knowles  wrote:
> 
> Seems like there has been a lot of progress on 
> https://github.com/raphw/byte-buddy/issues/1301 
> . Since it has been 
> identified, I think we can be pretty confident that the version downgrade is 
> the necessary part. So we can revert the PR for the release, then on main 
> branch we can proceed with unvendoring but keeping the same version.

+1 for this.

> BTW just noting for the thread that I also checked mvn dependency:tree of 
> Talend/beam-samples and confirmed that only Beam depends on bytebuddy so it 
> is not a dependency conflict.

Sorry, I forgot to mention that I'd checked this before I posted that issue on 
dev@ (to make sure that it depends only on one version of byte_buddy).
Thanks for highlighting this.

> I also googled the error message and found 
> https://stackoverflow.com/questions/51650074/apache-beam-invisible-parameter-type-exception
>  
> 
>  and https://issues.apache.org/jira/browse/BEAM-5061 
>  where using JDK 10 instead 
> of 8 causes a similar symptom but it does not seem related. It was never 
> directly addressed.

For me, it looks not very related since it’s about pretty old version of 
byte_buddy and in “beam-samples” we test a build with OpenJDK v8, v11, and even 
v17 and it fails in the same way for all of them.

—
Alexey

> 
> Kenn
> 
> On Wed, Aug 17, 2022 at 10:36 AM Kiley Sok  > wrote:
> PR to revert the change for the release 
> https://github.com/apache/beam/pull/22759 
> 
> 
> I'll rebuild a new RC once the tests pass and the PR is merged.
> 
> On Wed, Aug 17, 2022 at 8:16 AM Liam Miller-Cushon  > wrote:
> On Tue, Aug 16, 2022 at 2:42 PM Kiley Sok  > wrote:
> Liam, are we okay to roll back this change for this release?
> 
> No concerns from me with rolling back to unblock the release.
> 
> It looks like this is a change between bytebuddy 1.12.3 and 1.12.4. I filed 
> https://github.com/raphw/byte-buddy/issues/1301 
>  to get help understanding 
> what changed, it sounds like the change might be WAI but there's a suggested 
> fix. I will prepare a PR for that as a follow-up.

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

[Kenneth Knowles]

Seems like there has been a lot of progress on
https://github.com/raphw/byte-buddy/issues/1301. Since it has been
identified, I think we can be pretty confident that the version downgrade
is the necessary part. So we can revert the PR for the release, then on
main branch we can proceed with unvendoring but keeping the same version.

BTW just noting for the thread that I also checked mvn dependency:tree of
Talend/beam-samples and confirmed that only Beam depends on bytebuddy so it
is not a dependency conflict. I also googled the error message and found
https://stackoverflow.com/questions/51650074/apache-beam-invisible-parameter-type-exception
and https://issues.apache.org/jira/browse/BEAM-5061 where using JDK 10
instead of 8 causes a similar symptom but it does not seem related. It was
never directly addressed.

Kenn

On Wed, Aug 17, 2022 at 10:36 AM Kiley Sok  wrote:

> PR to revert the change for the release
> https://github.com/apache/beam/pull/22759
>
> I'll rebuild a new RC once the tests pass and the PR is merged.
>
> On Wed, Aug 17, 2022 at 8:16 AM Liam Miller-Cushon 
> wrote:
>
>> On Tue, Aug 16, 2022 at 2:42 PM Kiley Sok  wrote:
>>
>>> Liam, are we okay to roll back this change for this release?
>>>
>>
>> No concerns from me with rolling back to unblock the release.
>>
>> It looks like this is a change between bytebuddy 1.12.3 and 1.12.4. I
>> filed https://github.com/raphw/byte-buddy/issues/1301 to get help
>> understanding what changed, it sounds like the change might be WAI but
>> there's a suggested fix. I will prepare a PR for that as a follow-up.
>>
>

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

[Kiley Sok via dev]

PR to revert the change for the release
https://github.com/apache/beam/pull/22759

I'll rebuild a new RC once the tests pass and the PR is merged.

On Wed, Aug 17, 2022 at 8:16 AM Liam Miller-Cushon 
wrote:

> On Tue, Aug 16, 2022 at 2:42 PM Kiley Sok  wrote:
>
>> Liam, are we okay to roll back this change for this release?
>>
>
> No concerns from me with rolling back to unblock the release.
>
> It looks like this is a change between bytebuddy 1.12.3 and 1.12.4. I
> filed https://github.com/raphw/byte-buddy/issues/1301 to get help
> understanding what changed, it sounds like the change might be WAI but
> there's a suggested fix. I will prepare a PR for that as a follow-up.
>

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

[Liam Miller-Cushon via dev]

On Tue, Aug 16, 2022 at 2:42 PM Kiley Sok  wrote:

> Liam, are we okay to roll back this change for this release?
>

No concerns from me with rolling back to unblock the release.

It looks like this is a change between bytebuddy 1.12.3 and 1.12.4. I filed
https://github.com/raphw/byte-buddy/issues/1301 to get help understanding
what changed, it sounds like the change might be WAI but there's a
suggested fix. I will prepare a PR for that as a follow-up.

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

[Jan Lukavský]

I think it is more complicated. I validated the Java SDK with Flink 
Runner and it passed through definitely more complex tests than a simple 
Pipeline with DoFn [1].


 Jan

[1] https://github.com/datadrivencz/proxima-platform/pull/624

On 8/17/22 15:19, Alexey Romanenko wrote:




On 16 Aug 2022, at 23:23, Kenneth Knowles  wrote:

And as a follow up we should make sure there is some test that would 
exercise this, since that PR was green and was a while ago too and 
our postcommits did not catch it either.


I’m concerned that it was not caught with Beam tests - it has to fail 
with literally every Java Beam pipeline that contains, at least, new 
DoFn instance creation. Though, it fails only when we compile and run 
a pipeline outside of Beam codebase.


Does it mean that Beam tests for some reasons still use an old 
vendored byte-buddy version?


—
Alexey





Kenn

On Tue, Aug 16, 2022 at 12:50 PM Kiley Sok via dev 
 wrote:


cc: @Liam Miller-Cushon , who worked on
the bytebuddy update.

Liam, do you have any context on this error?

On Tue, Aug 16, 2022 at 10:11 AM Alexey Romanenko
 wrote:

I tested with "beam-samples" [1] and found that a rather
simple test pipeline fails [2] with this runtime error:

Error:
 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time
elapsed: 2.776 s <<< FAILURE! - in SerializationTest

5809
Error:
 SerializationTest.nonSerilizableTest  Time elapsed: 2.708 s
 <<< ERROR!

5810

org.apache.beam.vendor.guava.v26_0_jre.com.google.common.util.concurrent.UncheckedExecutionException:
java.lang.IllegalStateException: Invisible parameter type of
SerializationTest$1 arg0 for public
SerializationTest$1$DoFnInvoker(SerializationTest$1)

5811
Caused by: java.lang.IllegalStateException: Invisible
parameter type of SerializationTest$1 arg0 for public
SerializationTest$1$DoFnInvoker(SerializationTest$1)


Seems like that it’s caused by “bytebuddy” dependency update
[3] from version 1.11.0 to 1.12.9 and it was vendored before
(not sure if it’s related).

Downgrading the “bytebuddy” version to 1.11.0 fixes an error.

I’ve not yet gone deep into a cause of this problem but maybe
someone knows some details?

[1] https://github.com/Talend/beam-samples/
[2]

https://github.com/Talend/beam-samples/runs/7856722514?check_suite_focus=true

[3] https://github.com/apache/beam/pull/17317

—
Alexey


On 16 Aug 2022, at 17:54, Ritesh Ghorse via dev
 wrote:

+1 (non-binding), Validated Go SDK Quickstart on Direct and
Dataflow runner


On Tue, Aug 16, 2022 at 4:26 AM Jan Lukavský
 wrote:

+1 (non-binding)

Validated Java SDK with classical Flink Runner.

On 8/15/22 23:06, Chamikara Jayalath via dev wrote:

+1 as well
(I believe Kiley is addressing the container tags issue)

Thanks,
Cham

On Mon, Aug 15, 2022 at 1:00 PM Robert Bradshaw
 wrote:

+1 (binding).

I verified the release artifacts and signatures,
and ran a couple of
simple Python pipelines.

On Mon, Aug 15, 2022 at 12:40 PM Chamikara Jayalath
via dev
 wrote:
>
>
>
> On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok
 wrote:
>>
>> Thanks everyone!
>>
>> @Chamikara Jayalath The Spark issue is running
successfully for me, could you try it again? I'll
look into the container tags.
>
>
> Thanks. Regarding the Spark issue, it could just
be my setup then. Feel free to close the Github issue.
>
> - Cham
>
>>
>>
>> On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada
 wrote:
>>>
>>> +1 - I validated tests/build with existing
Dataflow Templates
>>> Best
>>> -P.
>>>
>>> On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via
dev  wrote:

 +1 - I validated python quickstarts on direct
runner.

 Thank you Kiley!



 On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via
dev  wrote:
>
> Hi everyone,
> Please review and vote on 

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

[Alexey Romanenko]

> On 16 Aug 2022, at 23:23, Kenneth Knowles  wrote:
> 
> And as a follow up we should make sure there is some test that would exercise 
> this, since that PR was green and was a while ago too and our postcommits did 
> not catch it either.

I’m concerned that it was not caught with Beam tests - it has to fail with 
literally every Java Beam pipeline that contains, at least, new DoFn instance 
creation. Though, it fails only when we compile and run a pipeline outside of 
Beam codebase.

Does it mean that Beam tests for some reasons still use an old vendored 
byte-buddy version?

—
Alexey




> Kenn
> 
> On Tue, Aug 16, 2022 at 12:50 PM Kiley Sok via dev  > wrote:
> cc: @Liam Miller-Cushon , who worked on the 
> bytebuddy update. 
> 
> Liam, do you have any context on this error?
> 
> On Tue, Aug 16, 2022 at 10:11 AM Alexey Romanenko  > wrote:
> I tested with "beam-samples" [1] and found that a rather simple test pipeline 
> fails [2] with this runtime error:
> 
> Error: 
>  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.776 s <<< 
> FAILURE! - in SerializationTest
> 
> 5809
> Error: 
>  SerializationTest.nonSerilizableTest  Time elapsed: 2.708 s  <<< ERROR!
> 
> 5810
> org.apache.beam.vendor.guava.v26_0_jre.com.google.common.util.concurrent.UncheckedExecutionException:
>  java.lang.IllegalStateException: Invisible parameter type of 
> SerializationTest$1 arg0 for public 
> SerializationTest$1$DoFnInvoker(SerializationTest$1)
> 
> 5811
> Caused by: java.lang.IllegalStateException: Invisible parameter type of 
> SerializationTest$1 arg0 for public 
> SerializationTest$1$DoFnInvoker(SerializationTest$1)
> 
> 
> Seems like that it’s caused by “bytebuddy” dependency update [3] from version 
> 1.11.0 to 1.12.9 and it was vendored before (not sure if it’s related).
> 
> Downgrading the “bytebuddy” version to 1.11.0 fixes an error. 
> 
> I’ve not yet gone deep into a cause of this problem but maybe someone knows 
> some details?
> 
> [1] https://github.com/Talend/beam-samples/ 
> 
> [2] 
> https://github.com/Talend/beam-samples/runs/7856722514?check_suite_focus=true 
> 
>  
> [3] https://github.com/apache/beam/pull/17317 
> 
> 
> —
> Alexey
> 
>> On 16 Aug 2022, at 17:54, Ritesh Ghorse via dev > > wrote:
>> 
>> +1 (non-binding), Validated Go SDK Quickstart on Direct and Dataflow runner
>> 
>> 
>> On Tue, Aug 16, 2022 at 4:26 AM Jan Lukavský > > wrote:
>> +1 (non-binding)
>> 
>> Validated Java SDK with classical Flink Runner.
>> 
>> On 8/15/22 23:06, Chamikara Jayalath via dev wrote:
>>> +1 as well
>>> (I believe Kiley is addressing the container tags issue)
>>> 
>>> Thanks,
>>> Cham
>>> 
>>> On Mon, Aug 15, 2022 at 1:00 PM Robert Bradshaw >> > wrote:
>>> +1 (binding).
>>> 
>>> I verified the release artifacts and signatures, and ran a couple of
>>> simple Python pipelines.
>>> 
>>> On Mon, Aug 15, 2022 at 12:40 PM Chamikara Jayalath via dev
>>> mailto:dev@beam.apache.org>> wrote:
>>> >
>>> >
>>> >
>>> > On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok >> > > wrote:
>>> >>
>>> >> Thanks everyone!
>>> >>
>>> >> @Chamikara Jayalath The Spark issue is running successfully for me, 
>>> >> could you try it again? I'll look into the container tags.
>>> >
>>> >
>>> > Thanks. Regarding the Spark issue, it could just be my setup then. Feel 
>>> > free to close the Github issue.
>>> >
>>> > - Cham
>>> >
>>> >>
>>> >>
>>> >> On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada >> >> > wrote:
>>> >>>
>>> >>> +1 - I validated tests/build with existing Dataflow Templates
>>> >>> Best
>>> >>> -P.
>>> >>>
>>> >>> On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev 
>>> >>> mailto:dev@beam.apache.org>> wrote:
>>> 
>>>  +1 - I validated python quickstarts on direct runner.
>>> 
>>>  Thank you Kiley!
>>> 
>>> 
>>> 
>>>  On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev >>  > wrote:
>>> >
>>> > Hi everyone,
>>> > Please review and vote on the release candidate #1 for the version 
>>> > 2.41.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:
>>> > * GitHub Release notes [1],
>>> > * the official Apache source release to be deployed to 
>>> > dist.apache.org  [2], which is signed with 
>>> > the 

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

[Kenneth Knowles]

I don't think so. The vendored version that Beam depends on has been
published and shouldn't need to be built again. Not sure if our build has
changed so that it builds the vendored stuff as part of the main build as
well, vs pulling it from maven central.

Kenn

On Tue, Aug 16, 2022 at 2:42 PM Kiley Sok  wrote:

> If we roll back, do we need to roll back +Lukasz Cwik 's 
> change
> [1] on master as well?
>
> Liam, are we okay to roll back this change for this release?
>
> [1] https://github.com/apache/beam/pull/22594
>
> On Tue, Aug 16, 2022 at 2:25 PM Kenneth Knowles  wrote:
>
>> Two options to unblock the release are:
>>
>> 1. Roll back https://github.com/apache/beam/pull/17317/files
>> 2. Downgrade unvendored bytebuddy to 1.11.0 (if the above doesn't work or
>> is too high risk)
>>
>> And as a follow up we should make sure there is some test that would
>> exercise this, since that PR was green and was a while ago too and our
>> postcommits did not catch it either.
>>
>> Kenn
>>
>> On Tue, Aug 16, 2022 at 12:50 PM Kiley Sok via dev 
>> wrote:
>>
>>> cc: @Liam Miller-Cushon , who worked on the
>>> bytebuddy update.
>>>
>>> Liam, do you have any context on this error?
>>>
>>> On Tue, Aug 16, 2022 at 10:11 AM Alexey Romanenko <
>>> aromanenko@gmail.com> wrote:
>>>
 I tested with "beam-samples" [1] and found that a rather simple test
 pipeline fails [2] with this runtime error:

 Error:
  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.776
 s <<< FAILURE! - in SerializationTest

 5809
 Error:
  SerializationTest.nonSerilizableTest  Time elapsed: 2.708 s  <<< ERROR!

 5810
 org.apache.beam.vendor.guava.v26_0_jre.com.google.common.util.concurrent.UncheckedExecutionException:
 java.lang.IllegalStateException: Invisible parameter type of
 SerializationTest$1 arg0 for public
 SerializationTest$1$DoFnInvoker(SerializationTest$1)

 5811
 Caused by: java.lang.IllegalStateException: Invisible parameter type of
 SerializationTest$1 arg0 for public
 SerializationTest$1$DoFnInvoker(SerializationTest$1)


 Seems like that it’s caused by “bytebuddy” dependency update [3] from
 version 1.11.0 to 1.12.9 and it was vendored before (not sure if it’s
 related).

 Downgrading the “bytebuddy” version to 1.11.0 fixes an error.

 I’ve not yet gone deep into a cause of this problem but maybe someone
 knows some details?

 [1] https://github.com/Talend/beam-samples/
 [2]
 https://github.com/Talend/beam-samples/runs/7856722514?check_suite_focus=true

 [3] https://github.com/apache/beam/pull/17317

 —
 Alexey

 On 16 Aug 2022, at 17:54, Ritesh Ghorse via dev 
 wrote:

 +1 (non-binding), Validated Go SDK Quickstart on Direct and Dataflow
 runner


 On Tue, Aug 16, 2022 at 4:26 AM Jan Lukavský  wrote:

> +1 (non-binding)
>
> Validated Java SDK with classical Flink Runner.
> On 8/15/22 23:06, Chamikara Jayalath via dev wrote:
>
> +1 as well
> (I believe Kiley is addressing the container tags issue)
>
> Thanks,
> Cham
>
> On Mon, Aug 15, 2022 at 1:00 PM Robert Bradshaw 
> wrote:
>
>> +1 (binding).
>>
>> I verified the release artifacts and signatures, and ran a couple of
>> simple Python pipelines.
>>
>> On Mon, Aug 15, 2022 at 12:40 PM Chamikara Jayalath via dev
>>  wrote:
>> >
>> >
>> >
>> > On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok 
>> wrote:
>> >>
>> >> Thanks everyone!
>> >>
>> >> @Chamikara Jayalath The Spark issue is running successfully for
>> me, could you try it again? I'll look into the container tags.
>> >
>> >
>> > Thanks. Regarding the Spark issue, it could just be my setup then.
>> Feel free to close the Github issue.
>> >
>> > - Cham
>> >
>> >>
>> >>
>> >> On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada 
>> wrote:
>> >>>
>> >>> +1 - I validated tests/build with existing Dataflow Templates
>> >>> Best
>> >>> -P.
>> >>>
>> >>> On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev <
>> dev@beam.apache.org> wrote:
>> 
>>  +1 - I validated python quickstarts on direct runner.
>> 
>>  Thank you Kiley!
>> 
>> 
>> 
>>  On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev <
>> dev@beam.apache.org> wrote:
>> >
>> > Hi everyone,
>> > Please review and vote on the release candidate #1 for the
>> version 2.41.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.
>> >
>> 

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

[Kiley Sok via dev]

If we roll back, do we need to roll back +Lukasz Cwik
's change
[1] on master as well?

Liam, are we okay to roll back this change for this release?

[1] https://github.com/apache/beam/pull/22594

On Tue, Aug 16, 2022 at 2:25 PM Kenneth Knowles  wrote:

> Two options to unblock the release are:
>
> 1. Roll back https://github.com/apache/beam/pull/17317/files
> 2. Downgrade unvendored bytebuddy to 1.11.0 (if the above doesn't work or
> is too high risk)
>
> And as a follow up we should make sure there is some test that would
> exercise this, since that PR was green and was a while ago too and our
> postcommits did not catch it either.
>
> Kenn
>
> On Tue, Aug 16, 2022 at 12:50 PM Kiley Sok via dev 
> wrote:
>
>> cc: @Liam Miller-Cushon , who worked on the bytebuddy
>> update.
>>
>> Liam, do you have any context on this error?
>>
>> On Tue, Aug 16, 2022 at 10:11 AM Alexey Romanenko <
>> aromanenko@gmail.com> wrote:
>>
>>> I tested with "beam-samples" [1] and found that a rather simple test
>>> pipeline fails [2] with this runtime error:
>>>
>>> Error:
>>>  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.776 s
>>> <<< FAILURE! - in SerializationTest
>>>
>>> 5809
>>> Error:
>>>  SerializationTest.nonSerilizableTest  Time elapsed: 2.708 s  <<< ERROR!
>>>
>>> 5810
>>> org.apache.beam.vendor.guava.v26_0_jre.com.google.common.util.concurrent.UncheckedExecutionException:
>>> java.lang.IllegalStateException: Invisible parameter type of
>>> SerializationTest$1 arg0 for public
>>> SerializationTest$1$DoFnInvoker(SerializationTest$1)
>>>
>>> 5811
>>> Caused by: java.lang.IllegalStateException: Invisible parameter type of
>>> SerializationTest$1 arg0 for public
>>> SerializationTest$1$DoFnInvoker(SerializationTest$1)
>>>
>>>
>>> Seems like that it’s caused by “bytebuddy” dependency update [3] from
>>> version 1.11.0 to 1.12.9 and it was vendored before (not sure if it’s
>>> related).
>>>
>>> Downgrading the “bytebuddy” version to 1.11.0 fixes an error.
>>>
>>> I’ve not yet gone deep into a cause of this problem but maybe someone
>>> knows some details?
>>>
>>> [1] https://github.com/Talend/beam-samples/
>>> [2]
>>> https://github.com/Talend/beam-samples/runs/7856722514?check_suite_focus=true
>>>
>>> [3] https://github.com/apache/beam/pull/17317
>>>
>>> —
>>> Alexey
>>>
>>> On 16 Aug 2022, at 17:54, Ritesh Ghorse via dev 
>>> wrote:
>>>
>>> +1 (non-binding), Validated Go SDK Quickstart on Direct and Dataflow
>>> runner
>>>
>>>
>>> On Tue, Aug 16, 2022 at 4:26 AM Jan Lukavský  wrote:
>>>
 +1 (non-binding)

 Validated Java SDK with classical Flink Runner.
 On 8/15/22 23:06, Chamikara Jayalath via dev wrote:

 +1 as well
 (I believe Kiley is addressing the container tags issue)

 Thanks,
 Cham

 On Mon, Aug 15, 2022 at 1:00 PM Robert Bradshaw 
 wrote:

> +1 (binding).
>
> I verified the release artifacts and signatures, and ran a couple of
> simple Python pipelines.
>
> On Mon, Aug 15, 2022 at 12:40 PM Chamikara Jayalath via dev
>  wrote:
> >
> >
> >
> > On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok 
> wrote:
> >>
> >> Thanks everyone!
> >>
> >> @Chamikara Jayalath The Spark issue is running successfully for me,
> could you try it again? I'll look into the container tags.
> >
> >
> > Thanks. Regarding the Spark issue, it could just be my setup then.
> Feel free to close the Github issue.
> >
> > - Cham
> >
> >>
> >>
> >> On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada 
> wrote:
> >>>
> >>> +1 - I validated tests/build with existing Dataflow Templates
> >>> Best
> >>> -P.
> >>>
> >>> On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev <
> dev@beam.apache.org> wrote:
> 
>  +1 - I validated python quickstarts on direct runner.
> 
>  Thank you Kiley!
> 
> 
> 
>  On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev <
> dev@beam.apache.org> wrote:
> >
> > Hi everyone,
> > Please review and vote on the release candidate #1 for the
> version 2.41.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:
> > * GitHub Release notes [1],
> > * the official Apache source release to be deployed to
> dist.apache.org [2], which is signed with the key with fingerprint
> 4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
> > * all artifacts to be deployed to the Maven Central Repository
> [4],
> > * source code tag "v2.41.0-RC1" [5],
> > * website pull 

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

[Kenneth Knowles]

Two options to unblock the release are:

1. Roll back https://github.com/apache/beam/pull/17317/files
2. Downgrade unvendored bytebuddy to 1.11.0 (if the above doesn't work or
is too high risk)

And as a follow up we should make sure there is some test that would
exercise this, since that PR was green and was a while ago too and our
postcommits did not catch it either.

Kenn

On Tue, Aug 16, 2022 at 12:50 PM Kiley Sok via dev 
wrote:

> cc: @Liam Miller-Cushon , who worked on the bytebuddy
> update.
>
> Liam, do you have any context on this error?
>
> On Tue, Aug 16, 2022 at 10:11 AM Alexey Romanenko <
> aromanenko@gmail.com> wrote:
>
>> I tested with "beam-samples" [1] and found that a rather simple test
>> pipeline fails [2] with this runtime error:
>>
>> Error:
>>  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.776 s
>> <<< FAILURE! - in SerializationTest
>>
>> 5809
>> Error:
>>  SerializationTest.nonSerilizableTest  Time elapsed: 2.708 s  <<< ERROR!
>>
>> 5810
>> org.apache.beam.vendor.guava.v26_0_jre.com.google.common.util.concurrent.UncheckedExecutionException:
>> java.lang.IllegalStateException: Invisible parameter type of
>> SerializationTest$1 arg0 for public
>> SerializationTest$1$DoFnInvoker(SerializationTest$1)
>>
>> 5811
>> Caused by: java.lang.IllegalStateException: Invisible parameter type of
>> SerializationTest$1 arg0 for public
>> SerializationTest$1$DoFnInvoker(SerializationTest$1)
>>
>>
>> Seems like that it’s caused by “bytebuddy” dependency update [3] from
>> version 1.11.0 to 1.12.9 and it was vendored before (not sure if it’s
>> related).
>>
>> Downgrading the “bytebuddy” version to 1.11.0 fixes an error.
>>
>> I’ve not yet gone deep into a cause of this problem but maybe someone
>> knows some details?
>>
>> [1] https://github.com/Talend/beam-samples/
>> [2]
>> https://github.com/Talend/beam-samples/runs/7856722514?check_suite_focus=true
>>
>> [3] https://github.com/apache/beam/pull/17317
>>
>> —
>> Alexey
>>
>> On 16 Aug 2022, at 17:54, Ritesh Ghorse via dev 
>> wrote:
>>
>> +1 (non-binding), Validated Go SDK Quickstart on Direct and Dataflow
>> runner
>>
>>
>> On Tue, Aug 16, 2022 at 4:26 AM Jan Lukavský  wrote:
>>
>>> +1 (non-binding)
>>>
>>> Validated Java SDK with classical Flink Runner.
>>> On 8/15/22 23:06, Chamikara Jayalath via dev wrote:
>>>
>>> +1 as well
>>> (I believe Kiley is addressing the container tags issue)
>>>
>>> Thanks,
>>> Cham
>>>
>>> On Mon, Aug 15, 2022 at 1:00 PM Robert Bradshaw 
>>> wrote:
>>>
 +1 (binding).

 I verified the release artifacts and signatures, and ran a couple of
 simple Python pipelines.

 On Mon, Aug 15, 2022 at 12:40 PM Chamikara Jayalath via dev
  wrote:
 >
 >
 >
 > On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok 
 wrote:
 >>
 >> Thanks everyone!
 >>
 >> @Chamikara Jayalath The Spark issue is running successfully for me,
 could you try it again? I'll look into the container tags.
 >
 >
 > Thanks. Regarding the Spark issue, it could just be my setup then.
 Feel free to close the Github issue.
 >
 > - Cham
 >
 >>
 >>
 >> On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada 
 wrote:
 >>>
 >>> +1 - I validated tests/build with existing Dataflow Templates
 >>> Best
 >>> -P.
 >>>
 >>> On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev <
 dev@beam.apache.org> wrote:
 
  +1 - I validated python quickstarts on direct runner.
 
  Thank you Kiley!
 
 
 
  On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev <
 dev@beam.apache.org> wrote:
 >
 > Hi everyone,
 > Please review and vote on the release candidate #1 for the
 version 2.41.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:
 > * GitHub Release notes [1],
 > * the official Apache source release to be deployed to
 dist.apache.org [2], which is signed with the key with fingerprint
 4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
 > * all artifacts to be deployed to the Maven Central Repository
 [4],
 > * source code tag "v2.41.0-RC1" [5],
 > * website pull request listing the release [6], the blog post
 [6], and publishing the API reference manual [7].
 > * Java artifacts were built with Gradle 7.4 and OpenJDK/Oracle
 JDK 1.8.0_232.
 > * Python artifacts are deployed along with the source release to
 the dist.apache.org [2] and PyPI[8].
 > * Validation sheet with a tab for 2.41.0 release to help with
 validation [9].
 

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

[Kiley Sok via dev]

cc: @Liam Miller-Cushon , who worked on the bytebuddy
update.

Liam, do you have any context on this error?

On Tue, Aug 16, 2022 at 10:11 AM Alexey Romanenko 
wrote:

> I tested with "beam-samples" [1] and found that a rather simple test
> pipeline fails [2] with this runtime error:
>
> Error:
>  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.776 s
> <<< FAILURE! - in SerializationTest
>
> 5809
> Error:
>  SerializationTest.nonSerilizableTest  Time elapsed: 2.708 s  <<< ERROR!
>
> 5810
> org.apache.beam.vendor.guava.v26_0_jre.com.google.common.util.concurrent.UncheckedExecutionException:
> java.lang.IllegalStateException: Invisible parameter type of
> SerializationTest$1 arg0 for public
> SerializationTest$1$DoFnInvoker(SerializationTest$1)
>
> 5811
> Caused by: java.lang.IllegalStateException: Invisible parameter type of
> SerializationTest$1 arg0 for public
> SerializationTest$1$DoFnInvoker(SerializationTest$1)
>
>
> Seems like that it’s caused by “bytebuddy” dependency update [3] from
> version 1.11.0 to 1.12.9 and it was vendored before (not sure if it’s
> related).
>
> Downgrading the “bytebuddy” version to 1.11.0 fixes an error.
>
> I’ve not yet gone deep into a cause of this problem but maybe someone
> knows some details?
>
> [1] https://github.com/Talend/beam-samples/
> [2]
> https://github.com/Talend/beam-samples/runs/7856722514?check_suite_focus=true
>
> [3] https://github.com/apache/beam/pull/17317
>
> —
> Alexey
>
> On 16 Aug 2022, at 17:54, Ritesh Ghorse via dev 
> wrote:
>
> +1 (non-binding), Validated Go SDK Quickstart on Direct and Dataflow runner
>
>
> On Tue, Aug 16, 2022 at 4:26 AM Jan Lukavský  wrote:
>
>> +1 (non-binding)
>>
>> Validated Java SDK with classical Flink Runner.
>> On 8/15/22 23:06, Chamikara Jayalath via dev wrote:
>>
>> +1 as well
>> (I believe Kiley is addressing the container tags issue)
>>
>> Thanks,
>> Cham
>>
>> On Mon, Aug 15, 2022 at 1:00 PM Robert Bradshaw 
>> wrote:
>>
>>> +1 (binding).
>>>
>>> I verified the release artifacts and signatures, and ran a couple of
>>> simple Python pipelines.
>>>
>>> On Mon, Aug 15, 2022 at 12:40 PM Chamikara Jayalath via dev
>>>  wrote:
>>> >
>>> >
>>> >
>>> > On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok 
>>> wrote:
>>> >>
>>> >> Thanks everyone!
>>> >>
>>> >> @Chamikara Jayalath The Spark issue is running successfully for me,
>>> could you try it again? I'll look into the container tags.
>>> >
>>> >
>>> > Thanks. Regarding the Spark issue, it could just be my setup then.
>>> Feel free to close the Github issue.
>>> >
>>> > - Cham
>>> >
>>> >>
>>> >>
>>> >> On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada 
>>> wrote:
>>> >>>
>>> >>> +1 - I validated tests/build with existing Dataflow Templates
>>> >>> Best
>>> >>> -P.
>>> >>>
>>> >>> On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev <
>>> dev@beam.apache.org> wrote:
>>> 
>>>  +1 - I validated python quickstarts on direct runner.
>>> 
>>>  Thank you Kiley!
>>> 
>>> 
>>> 
>>>  On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev <
>>> dev@beam.apache.org> wrote:
>>> >
>>> > Hi everyone,
>>> > Please review and vote on the release candidate #1 for the version
>>> 2.41.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:
>>> > * GitHub Release notes [1],
>>> > * the official Apache source release to be deployed to
>>> dist.apache.org [2], which is signed with the key with fingerprint
>>> 4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
>>> > * all artifacts to be deployed to the Maven Central Repository [4],
>>> > * source code tag "v2.41.0-RC1" [5],
>>> > * website pull request listing the release [6], the blog post [6],
>>> and publishing the API reference manual [7].
>>> > * Java artifacts were built with Gradle 7.4 and OpenJDK/Oracle JDK
>>> 1.8.0_232.
>>> > * Python artifacts are deployed along with the source release to
>>> the dist.apache.org [2] and PyPI[8].
>>> > * Validation sheet with a tab for 2.41.0 release to help with
>>> validation [9].
>>> > * Docker images published to Docker Hub [10].
>>> >
>>> > The vote will be open for at least 72 hours. It is adopted by
>>> majority approval, with at least 3 PMC affirmative votes.
>>> >
>>> > For guidelines on how to try the release in your projects, check
>>> out our blog post at https://beam.apache.org/blog/validate-beam-release/
>>> .
>>> >
>>> > Thanks,
>>> > Release Manager
>>> >
>>> > [1] https://github.com/apache/beam/milestone/3
>>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.41.0/
>>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> > 

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

[Alexey Romanenko]

I tested with "beam-samples" [1] and found that a rather simple test pipeline 
fails [2] with this runtime error:

Error: 
 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.776 s <<< 
FAILURE! - in SerializationTest

5809
Error: 
 SerializationTest.nonSerilizableTest  Time elapsed: 2.708 s  <<< ERROR!

5810
org.apache.beam.vendor.guava.v26_0_jre.com.google.common.util.concurrent.UncheckedExecutionException:
 java.lang.IllegalStateException: Invisible parameter type of 
SerializationTest$1 arg0 for public 
SerializationTest$1$DoFnInvoker(SerializationTest$1)

5811
Caused by: java.lang.IllegalStateException: Invisible parameter type of 
SerializationTest$1 arg0 for public 
SerializationTest$1$DoFnInvoker(SerializationTest$1)


Seems like that it’s caused by “bytebuddy” dependency update [3] from version 
1.11.0 to 1.12.9 and it was vendored before (not sure if it’s related).

Downgrading the “bytebuddy” version to 1.11.0 fixes an error. 

I’ve not yet gone deep into a cause of this problem but maybe someone knows 
some details?

[1] https://github.com/Talend/beam-samples/ 

[2] 
https://github.com/Talend/beam-samples/runs/7856722514?check_suite_focus=true 
[3] https://github.com/apache/beam/pull/17317 


—
Alexey

> On 16 Aug 2022, at 17:54, Ritesh Ghorse via dev  wrote:
> 
> +1 (non-binding), Validated Go SDK Quickstart on Direct and Dataflow runner
> 
> 
> On Tue, Aug 16, 2022 at 4:26 AM Jan Lukavský  > wrote:
> +1 (non-binding)
> 
> Validated Java SDK with classical Flink Runner.
> 
> On 8/15/22 23:06, Chamikara Jayalath via dev wrote:
>> +1 as well
>> (I believe Kiley is addressing the container tags issue)
>> 
>> Thanks,
>> Cham
>> 
>> On Mon, Aug 15, 2022 at 1:00 PM Robert Bradshaw > > wrote:
>> +1 (binding).
>> 
>> I verified the release artifacts and signatures, and ran a couple of
>> simple Python pipelines.
>> 
>> On Mon, Aug 15, 2022 at 12:40 PM Chamikara Jayalath via dev
>> mailto:dev@beam.apache.org>> wrote:
>> >
>> >
>> >
>> > On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok > > > wrote:
>> >>
>> >> Thanks everyone!
>> >>
>> >> @Chamikara Jayalath The Spark issue is running successfully for me, could 
>> >> you try it again? I'll look into the container tags.
>> >
>> >
>> > Thanks. Regarding the Spark issue, it could just be my setup then. Feel 
>> > free to close the Github issue.
>> >
>> > - Cham
>> >
>> >>
>> >>
>> >> On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada > >> > wrote:
>> >>>
>> >>> +1 - I validated tests/build with existing Dataflow Templates
>> >>> Best
>> >>> -P.
>> >>>
>> >>> On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev > >>> > wrote:
>> 
>>  +1 - I validated python quickstarts on direct runner.
>> 
>>  Thank you Kiley!
>> 
>> 
>> 
>>  On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev >  > wrote:
>> >
>> > Hi everyone,
>> > Please review and vote on the release candidate #1 for the version 
>> > 2.41.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:
>> > * GitHub Release notes [1],
>> > * the official Apache source release to be deployed to dist.apache.org 
>> >  [2], which is signed with the key with 
>> > fingerprint 4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
>> > * all artifacts to be deployed to the Maven Central Repository [4],
>> > * source code tag "v2.41.0-RC1" [5],
>> > * website pull request listing the release [6], the blog post [6], and 
>> > publishing the API reference manual [7].
>> > * Java artifacts were built with Gradle 7.4 and OpenJDK/Oracle JDK 
>> > 1.8.0_232.
>> > * Python artifacts are deployed along with the source release to the 
>> > dist.apache.org  [2] and PyPI[8].
>> > * Validation sheet with a tab for 2.41.0 release to help with 
>> > validation [9].
>> > * Docker images published to Docker Hub [10].
>> >
>> > The vote will be open for at least 72 hours. It is adopted by majority 
>> > approval, with at least 3 PMC affirmative votes.
>> >
>> > For guidelines on how to try the release in your projects, check out 
>> > our blog post at https://beam.apache.org/blog/validate-beam-release/ 
>> > .
>> >
>> > Thanks,
>> > Release Manager
>> >
>> > [1] https://github.com/apache/beam/milestone/3 
>> > 

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

[Ritesh Ghorse via dev]

+1 (non-binding), Validated Go SDK Quickstart on Direct and Dataflow runner


On Tue, Aug 16, 2022 at 4:26 AM Jan Lukavský  wrote:

> +1 (non-binding)
>
> Validated Java SDK with classical Flink Runner.
> On 8/15/22 23:06, Chamikara Jayalath via dev wrote:
>
> +1 as well
> (I believe Kiley is addressing the container tags issue)
>
> Thanks,
> Cham
>
> On Mon, Aug 15, 2022 at 1:00 PM Robert Bradshaw 
> wrote:
>
>> +1 (binding).
>>
>> I verified the release artifacts and signatures, and ran a couple of
>> simple Python pipelines.
>>
>> On Mon, Aug 15, 2022 at 12:40 PM Chamikara Jayalath via dev
>>  wrote:
>> >
>> >
>> >
>> > On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok  wrote:
>> >>
>> >> Thanks everyone!
>> >>
>> >> @Chamikara Jayalath The Spark issue is running successfully for me,
>> could you try it again? I'll look into the container tags.
>> >
>> >
>> > Thanks. Regarding the Spark issue, it could just be my setup then. Feel
>> free to close the Github issue.
>> >
>> > - Cham
>> >
>> >>
>> >>
>> >> On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada 
>> wrote:
>> >>>
>> >>> +1 - I validated tests/build with existing Dataflow Templates
>> >>> Best
>> >>> -P.
>> >>>
>> >>> On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev <
>> dev@beam.apache.org> wrote:
>> 
>>  +1 - I validated python quickstarts on direct runner.
>> 
>>  Thank you Kiley!
>> 
>> 
>> 
>>  On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev <
>> dev@beam.apache.org> wrote:
>> >
>> > Hi everyone,
>> > Please review and vote on the release candidate #1 for the version
>> 2.41.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:
>> > * GitHub Release notes [1],
>> > * the official Apache source release to be deployed to
>> dist.apache.org [2], which is signed with the key with fingerprint
>> 4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
>> > * all artifacts to be deployed to the Maven Central Repository [4],
>> > * source code tag "v2.41.0-RC1" [5],
>> > * website pull request listing the release [6], the blog post [6],
>> and publishing the API reference manual [7].
>> > * Java artifacts were built with Gradle 7.4 and OpenJDK/Oracle JDK
>> 1.8.0_232.
>> > * Python artifacts are deployed along with the source release to
>> the dist.apache.org [2] and PyPI[8].
>> > * Validation sheet with a tab for 2.41.0 release to help with
>> validation [9].
>> > * Docker images published to Docker Hub [10].
>> >
>> > The vote will be open for at least 72 hours. It is adopted by
>> majority approval, with at least 3 PMC affirmative votes.
>> >
>> > For guidelines on how to try the release in your projects, check
>> out our blog post at https://beam.apache.org/blog/validate-beam-release/.
>> >
>> > Thanks,
>> > Release Manager
>> >
>> > [1] https://github.com/apache/beam/milestone/3
>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.41.0/
>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> > [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1282/
>> > [5] https://github.com/apache/beam/tree/v2.41.0-RC1
>> > [6] https://github.com/apache/beam/pull/22706
>> > [7] https://github.com/apache/beam-site/pull/633
>> > [8] https://pypi.org/project/apache-beam/2.41.0rc1/
>> > [9]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=331459080
>> > [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>>
>

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

[Jan Lukavský]

+1 (non-binding)

Validated Java SDK with classical Flink Runner.

On 8/15/22 23:06, Chamikara Jayalath via dev wrote:

+1 as well
(I believe Kiley is addressing the container tags issue)

Thanks,
Cham

On Mon, Aug 15, 2022 at 1:00 PM Robert Bradshaw  
wrote:


+1 (binding).

I verified the release artifacts and signatures, and ran a couple of
simple Python pipelines.

On Mon, Aug 15, 2022 at 12:40 PM Chamikara Jayalath via dev
 wrote:
>
>
>
> On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok 
wrote:
>>
>> Thanks everyone!
>>
>> @Chamikara Jayalath The Spark issue is running successfully for
me, could you try it again? I'll look into the container tags.
>
>
> Thanks. Regarding the Spark issue, it could just be my setup
then. Feel free to close the Github issue.
>
> - Cham
>
>>
>>
>> On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada
 wrote:
>>>
>>> +1 - I validated tests/build with existing Dataflow Templates
>>> Best
>>> -P.
>>>
>>> On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev
 wrote:

 +1 - I validated python quickstarts on direct runner.

 Thank you Kiley!



 On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev
 wrote:
>
> Hi everyone,
> Please review and vote on the release candidate #1 for the
version 2.41.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:
> * GitHub Release notes [1],
> * the official Apache source release to be deployed to
dist.apache.org  [2], which is signed with
the key with fingerprint 4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
> * all artifacts to be deployed to the Maven Central
Repository [4],
> * source code tag "v2.41.0-RC1" [5],
> * website pull request listing the release [6], the blog
post [6], and publishing the API reference manual [7].
> * Java artifacts were built with Gradle 7.4 and
OpenJDK/Oracle JDK 1.8.0_232.
> * Python artifacts are deployed along with the source
release to the dist.apache.org  [2] and
PyPI[8].
> * Validation sheet with a tab for 2.41.0 release to help
with validation [9].
> * Docker images published to Docker Hub [10].
>
> The vote will be open for at least 72 hours. It is adopted
by majority approval, with at least 3 PMC affirmative votes.
>
> For guidelines on how to try the release in your projects,
check out our blog post at
https://beam.apache.org/blog/validate-beam-release/.
>
> Thanks,
> Release Manager
>
> [1] https://github.com/apache/beam/milestone/3
> [2] https://dist.apache.org/repos/dist/dev/beam/2.41.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4]
https://repository.apache.org/content/repositories/orgapachebeam-1282/
> [5] https://github.com/apache/beam/tree/v2.41.0-RC1
> [6] https://github.com/apache/beam/pull/22706
> [7] https://github.com/apache/beam-site/pull/633
> [8] https://pypi.org/project/apache-beam/2.41.0rc1/
> [9]

https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=331459080
> [10]
https://hub.docker.com/search?q=apache%2Fbeam=image

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

[Chamikara Jayalath via dev]

+1 as well
(I believe Kiley is addressing the container tags issue)

Thanks,
Cham

On Mon, Aug 15, 2022 at 1:00 PM Robert Bradshaw  wrote:

> +1 (binding).
>
> I verified the release artifacts and signatures, and ran a couple of
> simple Python pipelines.
>
> On Mon, Aug 15, 2022 at 12:40 PM Chamikara Jayalath via dev
>  wrote:
> >
> >
> >
> > On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok  wrote:
> >>
> >> Thanks everyone!
> >>
> >> @Chamikara Jayalath The Spark issue is running successfully for me,
> could you try it again? I'll look into the container tags.
> >
> >
> > Thanks. Regarding the Spark issue, it could just be my setup then. Feel
> free to close the Github issue.
> >
> > - Cham
> >
> >>
> >>
> >> On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada 
> wrote:
> >>>
> >>> +1 - I validated tests/build with existing Dataflow Templates
> >>> Best
> >>> -P.
> >>>
> >>> On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev <
> dev@beam.apache.org> wrote:
> 
>  +1 - I validated python quickstarts on direct runner.
> 
>  Thank you Kiley!
> 
> 
> 
>  On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev <
> dev@beam.apache.org> wrote:
> >
> > Hi everyone,
> > Please review and vote on the release candidate #1 for the version
> 2.41.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:
> > * GitHub Release notes [1],
> > * the official Apache source release to be deployed to
> dist.apache.org [2], which is signed with the key with fingerprint
> 4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "v2.41.0-RC1" [5],
> > * website pull request listing the release [6], the blog post [6],
> and publishing the API reference manual [7].
> > * Java artifacts were built with Gradle 7.4 and OpenJDK/Oracle JDK
> 1.8.0_232.
> > * Python artifacts are deployed along with the source release to the
> dist.apache.org [2] and PyPI[8].
> > * Validation sheet with a tab for 2.41.0 release to help with
> validation [9].
> > * Docker images published to Docker Hub [10].
> >
> > The vote will be open for at least 72 hours. It is adopted by
> majority approval, with at least 3 PMC affirmative votes.
> >
> > For guidelines on how to try the release in your projects, check out
> our blog post at https://beam.apache.org/blog/validate-beam-release/.
> >
> > Thanks,
> > Release Manager
> >
> > [1] https://github.com/apache/beam/milestone/3
> > [2] https://dist.apache.org/repos/dist/dev/beam/2.41.0/
> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > [4]
> https://repository.apache.org/content/repositories/orgapachebeam-1282/
> > [5] https://github.com/apache/beam/tree/v2.41.0-RC1
> > [6] https://github.com/apache/beam/pull/22706
> > [7] https://github.com/apache/beam-site/pull/633
> > [8] https://pypi.org/project/apache-beam/2.41.0rc1/
> > [9]
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=331459080
> > [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>

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

[Robert Bradshaw via dev]

+1 (binding).

I verified the release artifacts and signatures, and ran a couple of
simple Python pipelines.

On Mon, Aug 15, 2022 at 12:40 PM Chamikara Jayalath via dev
 wrote:
>
>
>
> On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok  wrote:
>>
>> Thanks everyone!
>>
>> @Chamikara Jayalath The Spark issue is running successfully for me, could 
>> you try it again? I'll look into the container tags.
>
>
> Thanks. Regarding the Spark issue, it could just be my setup then. Feel free 
> to close the Github issue.
>
> - Cham
>
>>
>>
>> On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada  wrote:
>>>
>>> +1 - I validated tests/build with existing Dataflow Templates
>>> Best
>>> -P.
>>>
>>> On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev  
>>> wrote:

 +1 - I validated python quickstarts on direct runner.

 Thank you Kiley!



 On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev  
 wrote:
>
> Hi everyone,
> Please review and vote on the release candidate #1 for the version 
> 2.41.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:
> * GitHub Release notes [1],
> * the official Apache source release to be deployed to dist.apache.org 
> [2], which is signed with the key with fingerprint 
> 4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.41.0-RC1" [5],
> * website pull request listing the release [6], the blog post [6], and 
> publishing the API reference manual [7].
> * Java artifacts were built with Gradle 7.4 and OpenJDK/Oracle JDK 
> 1.8.0_232.
> * Python artifacts are deployed along with the source release to the 
> dist.apache.org [2] and PyPI[8].
> * Validation sheet with a tab for 2.41.0 release to help with validation 
> [9].
> * Docker images published to Docker Hub [10].
>
> The vote will be open for at least 72 hours. It is adopted by majority 
> approval, with at least 3 PMC affirmative votes.
>
> For guidelines on how to try the release in your projects, check out our 
> blog post at https://beam.apache.org/blog/validate-beam-release/.
>
> Thanks,
> Release Manager
>
> [1] https://github.com/apache/beam/milestone/3
> [2] https://dist.apache.org/repos/dist/dev/beam/2.41.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/orgapachebeam-1282/
> [5] https://github.com/apache/beam/tree/v2.41.0-RC1
> [6] https://github.com/apache/beam/pull/22706
> [7] https://github.com/apache/beam-site/pull/633
> [8] https://pypi.org/project/apache-beam/2.41.0rc1/
> [9] 
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=331459080
> [10] https://hub.docker.com/search?q=apache%2Fbeam=image

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

[Chamikara Jayalath via dev]

On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok  wrote:

> Thanks everyone!
>
> @Chamikara Jayalath  The Spark issue is running
> successfully for me, could you try it again? I'll look into the container
> tags.
>

Thanks. Regarding the Spark issue, it could just be my setup then. Feel
free to close the Github issue.

- Cham


>
> On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada  wrote:
>
>> +1 - I validated tests/build with existing Dataflow Templates
>> Best
>> -P.
>>
>> On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev 
>> wrote:
>>
>>> +1 - I validated python quickstarts on direct runner.
>>>
>>> Thank you Kiley!
>>>
>>>
>>>
>>> On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev 
>>> wrote:
>>>
 Hi everyone,
 Please review and vote on the release candidate #1 for the version
 2.41.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:
 * GitHub Release notes [1],
 * the official Apache source release to be deployed to dist.apache.org
 [2], which is signed with the key with fingerprint
 4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
 * all artifacts to be deployed to the Maven Central Repository [4],
 * source code tag "v2.41.0-RC1" [5],
 * website pull request listing the release [6], the blog post [6], and
 publishing the API reference manual [7].
 * Java artifacts were built with Gradle 7.4 and OpenJDK/Oracle JDK
 1.8.0_232.
 * Python artifacts are deployed along with the source release to the
 dist.apache.org [2] and PyPI[8].
 * Validation sheet with a tab for 2.41.0 release to help with
 validation [9].
 * Docker images published to Docker Hub [10].

 The vote will be open for at least 72 hours. It is adopted by majority
 approval, with at least 3 PMC affirmative votes.

 For guidelines on how to try the release in your projects, check out
 our blog post at https://beam.apache.org/blog/validate-beam-release/.

 Thanks,
 Release Manager

 [1] https://github.com/apache/beam/milestone/3
 [2] https://dist.apache.org/repos/dist/dev/beam/2.41.0/
 [3] https://dist.apache.org/repos/dist/release/beam/KEYS
 [4]
 https://repository.apache.org/content/repositories/orgapachebeam-1282/
 [5] https://github.com/apache/beam/tree/v2.41.0-RC1
 [6] https://github.com/apache/beam/pull/22706
 [7] https://github.com/apache/beam-site/pull/633
 [8] https://pypi.org/project/apache-beam/2.41.0rc1/
 [9]
 https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=331459080
 [10] https://hub.docker.com/search?q=apache%2Fbeam=image

>>>

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

[Kiley Sok via dev]

Thanks everyone!

@Chamikara Jayalath  The Spark issue is running
successfully for me, could you try it again? I'll look into the container
tags.

On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada  wrote:

> +1 - I validated tests/build with existing Dataflow Templates
> Best
> -P.
>
> On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev 
> wrote:
>
>> +1 - I validated python quickstarts on direct runner.
>>
>> Thank you Kiley!
>>
>>
>>
>> On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev 
>> wrote:
>>
>>> Hi everyone,
>>> Please review and vote on the release candidate #1 for the version
>>> 2.41.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:
>>> * GitHub Release notes [1],
>>> * the official Apache source release to be deployed to dist.apache.org
>>> [2], which is signed with the key with fingerprint
>>> 4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>> * source code tag "v2.41.0-RC1" [5],
>>> * website pull request listing the release [6], the blog post [6], and
>>> publishing the API reference manual [7].
>>> * Java artifacts were built with Gradle 7.4 and OpenJDK/Oracle JDK
>>> 1.8.0_232.
>>> * Python artifacts are deployed along with the source release to the
>>> dist.apache.org [2] and PyPI[8].
>>> * Validation sheet with a tab for 2.41.0 release to help with validation
>>> [9].
>>> * Docker images published to Docker Hub [10].
>>>
>>> The vote will be open for at least 72 hours. It is adopted by majority
>>> approval, with at least 3 PMC affirmative votes.
>>>
>>> For guidelines on how to try the release in your projects, check out our
>>> blog post at https://beam.apache.org/blog/validate-beam-release/.
>>>
>>> Thanks,
>>> Release Manager
>>>
>>> [1] https://github.com/apache/beam/milestone/3
>>> [2] https://dist.apache.org/repos/dist/dev/beam/2.41.0/
>>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> [4]
>>> https://repository.apache.org/content/repositories/orgapachebeam-1282/
>>> [5] https://github.com/apache/beam/tree/v2.41.0-RC1
>>> [6] https://github.com/apache/beam/pull/22706
>>> [7] https://github.com/apache/beam-site/pull/633
>>> [8] https://pypi.org/project/apache-beam/2.41.0rc1/
>>> [9]
>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=331459080
>>> [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>>>
>>

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

[Pablo Estrada via dev]

+1 - I validated tests/build with existing Dataflow Templates
Best
-P.

On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev 
wrote:

> +1 - I validated python quickstarts on direct runner.
>
> Thank you Kiley!
>
>
>
> On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev 
> wrote:
>
>> Hi everyone,
>> Please review and vote on the release candidate #1 for the version
>> 2.41.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:
>> * GitHub Release notes [1],
>> * the official Apache source release to be deployed to dist.apache.org
>> [2], which is signed with the key with fingerprint
>> 4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
>> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag "v2.41.0-RC1" [5],
>> * website pull request listing the release [6], the blog post [6], and
>> publishing the API reference manual [7].
>> * Java artifacts were built with Gradle 7.4 and OpenJDK/Oracle JDK
>> 1.8.0_232.
>> * Python artifacts are deployed along with the source release to the
>> dist.apache.org [2] and PyPI[8].
>> * Validation sheet with a tab for 2.41.0 release to help with validation
>> [9].
>> * Docker images published to Docker Hub [10].
>>
>> The vote will be open for at least 72 hours. It is adopted by majority
>> approval, with at least 3 PMC affirmative votes.
>>
>> For guidelines on how to try the release in your projects, check out our
>> blog post at https://beam.apache.org/blog/validate-beam-release/.
>>
>> Thanks,
>> Release Manager
>>
>> [1] https://github.com/apache/beam/milestone/3
>> [2] https://dist.apache.org/repos/dist/dev/beam/2.41.0/
>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1282/
>> [5] https://github.com/apache/beam/tree/v2.41.0-RC1
>> [6] https://github.com/apache/beam/pull/22706
>> [7] https://github.com/apache/beam-site/pull/633
>> [8] https://pypi.org/project/apache-beam/2.41.0rc1/
>> [9]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=331459080
>> [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>>
>

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

[Chamikara Jayalath via dev]

I ran some validations and noticed the following.

* Dataflow Java/Python containers now have the suffix "rc1' while for the
previous releases I tested they used to have the same container ID as the
final release. I suspect this is just a process change for Dataflow.

* Spark quickstart keeps failing when I run manually using the instructions
provided in the release guide [1]. All other quickstarts pass. Not sure if
the instructions for running the Spark test is just incorrect. Filed
https://github.com/apache/beam/issues/22728.

Updated the spreadsheet with the tests I ran.

Thanks,
Cham

[1]
https://beam.apache.org/contribute/release-guide/#run-validations-manually


On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev 
wrote:

> +1 - I validated python quickstarts on direct runner.
>
> Thank you Kiley!
>
>
>
> On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev 
> wrote:
>
>> Hi everyone,
>> Please review and vote on the release candidate #1 for the version
>> 2.41.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:
>> * GitHub Release notes [1],
>> * the official Apache source release to be deployed to dist.apache.org
>> [2], which is signed with the key with fingerprint
>> 4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
>> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag "v2.41.0-RC1" [5],
>> * website pull request listing the release [6], the blog post [6], and
>> publishing the API reference manual [7].
>> * Java artifacts were built with Gradle 7.4 and OpenJDK/Oracle JDK
>> 1.8.0_232.
>> * Python artifacts are deployed along with the source release to the
>> dist.apache.org [2] and PyPI[8].
>> * Validation sheet with a tab for 2.41.0 release to help with validation
>> [9].
>> * Docker images published to Docker Hub [10].
>>
>> The vote will be open for at least 72 hours. It is adopted by majority
>> approval, with at least 3 PMC affirmative votes.
>>
>> For guidelines on how to try the release in your projects, check out our
>> blog post at https://beam.apache.org/blog/validate-beam-release/.
>>
>> Thanks,
>> Release Manager
>>
>> [1] https://github.com/apache/beam/milestone/3
>> [2] https://dist.apache.org/repos/dist/dev/beam/2.41.0/
>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1282/
>> [5] https://github.com/apache/beam/tree/v2.41.0-RC1
>> [6] https://github.com/apache/beam/pull/22706
>> [7] https://github.com/apache/beam-site/pull/633
>> [8] https://pypi.org/project/apache-beam/2.41.0rc1/
>> [9]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=331459080
>> [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>>
>

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

[Ahmet Altay via dev]

+1 - I validated python quickstarts on direct runner.

Thank you Kiley!



On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev 
wrote:

> Hi everyone,
> Please review and vote on the release candidate #1 for the version 2.41.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:
> * GitHub Release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
> [2], which is signed with the key with fingerprint
> 4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.41.0-RC1" [5],
> * website pull request listing the release [6], the blog post [6], and
> publishing the API reference manual [7].
> * Java artifacts were built with Gradle 7.4 and OpenJDK/Oracle JDK
> 1.8.0_232.
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2] and PyPI[8].
> * Validation sheet with a tab for 2.41.0 release to help with validation
> [9].
> * Docker images published to Docker Hub [10].
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> For guidelines on how to try the release in your projects, check out our
> blog post at https://beam.apache.org/blog/validate-beam-release/.
>
> Thanks,
> Release Manager
>
> [1] https://github.com/apache/beam/milestone/3
> [2] https://dist.apache.org/repos/dist/dev/beam/2.41.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/orgapachebeam-1282/
> [5] https://github.com/apache/beam/tree/v2.41.0-RC1
> [6] https://github.com/apache/beam/pull/22706
> [7] https://github.com/apache/beam-site/pull/633
> [8] https://pypi.org/project/apache-beam/2.41.0rc1/
> [9]
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=331459080
> [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>

[VOTE] Release 2.41.0, release candidate #1

[Kiley Sok via dev]

Hi everyone,
Please review and vote on the release candidate #1 for the version 2.41.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:
* GitHub Release notes [1],
* the official Apache source release to be deployed to dist.apache.org [2],
which is signed with the key with fingerprint
4D5731CC0AA38097D091EB091E7B28884452AE5D [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "v2.41.0-RC1" [5],
* website pull request listing the release [6], the blog post [6], and
publishing the API reference manual [7].
* Java artifacts were built with Gradle 7.4 and OpenJDK/Oracle JDK
1.8.0_232.
* Python artifacts are deployed along with the source release to the
dist.apache.org [2] and PyPI[8].
* Validation sheet with a tab for 2.41.0 release to help with validation
[9].
* Docker images published to Docker Hub [10].

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

For guidelines on how to try the release in your projects, check out our
blog post at https://beam.apache.org/blog/validate-beam-release/.

Thanks,
Release Manager

[1] https://github.com/apache/beam/milestone/3
[2] https://dist.apache.org/repos/dist/dev/beam/2.41.0/
[3] https://dist.apache.org/repos/dist/release/beam/KEYS
[4] https://repository.apache.org/content/repositories/orgapachebeam-1282/
[5] https://github.com/apache/beam/tree/v2.41.0-RC1
[6] https://github.com/apache/beam/pull/22706
[7] https://github.com/apache/beam-site/pull/633
[8] https://pypi.org/project/apache-beam/2.41.0rc1/
[9]
https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=331459080
[10] https://hub.docker.com/search?q=apache%2Fbeam=image