+1 to include the fix for https://issues.apache.org/jira/browse/BEAM-12628 ! 🙏
Thanks, Kirill On Thu, Aug 19, 2021 at 8:29 PM Claire McGinty <[email protected]> wrote: > Hi! To add on, would you also consider including the cherry-picked commit > from > https://issues.apache.org/jira/browse/BEAM-12628 since it does include a > bug fix? > > -Claire > > On Thu, Aug 19, 2021 at 8:26 PM Sayat Satybaldiyev < > [email protected]> wrote: > >> Hello Ankur, >> >> I am wondering would you consider having commits from this PRs in the >> release if I make cherry-picks commits to resolve the issue with BQ write >> connector? >> >> https://github.com/apache/beam/pull/15237 >> https://github.com/apache/beam/pull/15352 >> >> On Mon, Aug 16, 2021 at 9:59 AM Ankur Goenka <[email protected]> wrote: >> >>> The issue regarding Dataflow Validation is resolved. Will do the >>> validation and post RC1 for voting once the validation is done. >>> >>> On Tue, Aug 10, 2021 at 9:22 PM Ankur Goenka <[email protected]> wrote: >>> >>>> For the release branch release-2.32.0 >>>> <https://github.com/apache/beam/tree/release-2.32.0> is the right one. >>>> I think 2.32 was created by mistake somewhere along the way. >>>> >>>> The 2 blocking issues 123723 and 12676 seems to have the same testing >>>> project issue tracked in the b/195313999 >>>> <https://buganizer.corp.google.com/195313999> I am not waiting on the >>>> fix for this issue as this is only a test configuration issue. >>>> >>>> I am in the process of promoting RC1 for validation which should be out >>>> in another hour. >>>> >>>> PR https://github.com/apache/beam/pull/15237 doesn't fix a regression >>>> so it's not a blocker. I will pick it up if we endup creating a new RC. >>>> >>>> On Tue, Aug 10, 2021 at 1:48 PM Luke Cwik <[email protected]> wrote: >>>> >>>>> Buquian doesn't seem to have a JIRA account to reassign it >>>>> appropriately. Buquian can you create one and provide your JIRA user name? >>>>> >>>>> Slava you are a contributor in JIRA so I believe you should be able to >>>>> reassign the issue. Were you logged into JIRA? >>>>> >>>>> On Tue, Aug 10, 2021 at 1:26 PM Slava Chernyak <[email protected]> >>>>> wrote: >>>>> >>>>>> FYI I believe (https://issues.apache.org/jira/browse/BEAM-12676) is >>>>>> assigned to me by mistake. I dont have permissions to change the issue >>>>>> though. Buquian has a solution for that issue. >>>>>> >>>>>> On Tue, Aug 10, 2021 at 1:22 PM Luke Cwik <[email protected]> wrote: >>>>>> >>>>>>> The remaining open issues are all related to the test failures in >>>>>>> the apache-beam-testing project due to b/195313999 >>>>>>> <https://buganizer.corp.google.com/195313999>. This is also >>>>>>> impacting out precommits for open PRs making it difficult for the Apache >>>>>>> Beam community to get a green signal before merging code so code is >>>>>>> being >>>>>>> merged with assumptions that the failure is due to the streaming issue. >>>>>>> >>>>>>> Ahmet, I added you to the thread that has more details as well in >>>>>>> https://mail.google.com/chat/u/0/#chat/space/AAAAeuPqsMg/Rm6rIg06mnc >>>>>>> >>>>>>> On Tue, Aug 10, 2021 at 11:01 AM Pablo Estrada <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> I'd like to request that we also include a cherry-pick for >>>>>>>> https://github.com/apache/beam/pull/15237 >>>>>>>> >>>>>>>> On Tue, Aug 10, 2021 at 10:59 AM Luke Cwik <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> +Kiley Sok <[email protected]> as previous plat-mon. >>>>>>>>> >>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723 is the same as >>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12699 and is due to a >>>>>>>>> key negotiation error between the worker and streaming engine failing >>>>>>>>> so no >>>>>>>>> work is done causing the job to fail. >>>>>>>>> >>>>>>>>> Kiley has a comment that it seems as though this is a known issue. >>>>>>>>> >>>>>>>>> On Tue, Aug 10, 2021 at 10:36 AM Ahmet Altay <[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Ankur, how is the release coming along? >>>>>>>>>> >>>>>>>>>> I noticed there are 2 open blockers: >>>>>>>>>> - One assigned to @Slava Chernyak <[email protected]> - Could >>>>>>>>>> you check with Slava, he may not be aware that this is a release >>>>>>>>>> blocker. ( >>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12676) >>>>>>>>>> - One unassigned. Could you find someone who could help? ( @Lukasz >>>>>>>>>> Cwik <[email protected]> ?) ( >>>>>>>>>> https://issues.apache.org/jira/browse/BEAM-12723) >>>>>>>>>> >>>>>>>>>> Ahmet >>>>>>>>>> >>>>>>>>>> On Thu, Aug 5, 2021 at 4:09 AM Alexey Romanenko < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> I noticed that we seems to have two branches for this release: >>>>>>>>>>> "release-2.32" (https://github.com/apache/beam/tree/release-2.32) >>>>>>>>>>> and "release-2.32.0” ( >>>>>>>>>>> https://github.com/apache/beam/tree/release-2.32.0) >>>>>>>>>>> >>>>>>>>>>> Is it intended or not? Would it better to keep only one to avoid >>>>>>>>>>> a confusion? >>>>>>>>>>> >>>>>>>>>>> — >>>>>>>>>>> Alexey >>>>>>>>>>> >>>>>>>>>>> On 7 Jul 2021, at 18:20, Ankur Goenka <[email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>> Hi All, >>>>>>>>>>> >>>>>>>>>>> Beam 2.32.0 release is scheduled to be cut on July 14th >>>>>>>>>>> (Wednesday) and released by Aug 18th according to the release >>>>>>>>>>> calendar [1]. >>>>>>>>>>> >>>>>>>>>>> If there are no objections then I would like to nominate myself >>>>>>>>>>> to do this release. >>>>>>>>>>> Sorry for the shorter notice as I was OOO for an extended period >>>>>>>>>>> of time. >>>>>>>>>>> Please review your bug list and mark the blockers as blocker for >>>>>>>>>>> the release and move non blockers to the next release by July 14th. >>>>>>>>>>> >>>>>>>>>>> Please let me know if you have any questions. >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> Ankur >>>>>>>>>>> >>>>>>>>>>> [1] >>>>>>>>>>> https://calendar.google.com/calendar/u/0/[email protected]&ctz=America/Los_Angeles >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>> >>>>>> -- >>>>>> Thanks, >>>>>> - Slava Chernyak >>>>>> >>>>> >> >> -- >> >> >> Sayat Satybaldyev >> >> Cruise >> >> >> *Confidentiality Note:* We care about protecting our proprietary >> information, confidential material, and trade secrets. This message may >> contain some or all of those things. Cruise will suffer material harm if >> anyone other than the intended recipient disseminates or takes any action >> based on this message. If you have received this message (including any >> attachments) in error, please delete it immediately and notify the sender >> promptly. > >
