[Result][VOTE] Vendored Dependencies Release beam-vendor-grpc-1_60_1
Hi everyone, I'm happy to announce that we have unanimously approved this release. There are three approving votes, three of which are binding: * Kenneth Knowles * Robert Bradshaw * Chamikara Jayalath There are no disapproving votes. I will begin finalizing the release. Thanks everyone! -- Yi Hu, (he/him/his) Software Engineer
Re: [VOTE] Vendored Dependencies Release
+1 (binding). Thanks, Cham On Mon, Jan 22, 2024 at 7:40 AM Yi Hu via dev wrote: > > Notably, the vendored artifact has no impact on the repo until the > version used is also bumped. > > That is correct. The PR that actually bump the version then the change > takes effect will be like https://github.com/apache/beam/pull/29976 > > On Mon, Jan 22, 2024 at 10:11 AM Kenneth Knowles wrote: > >> Notably, the vendored artifact has no impact on the repo until the >> version used is also bumped, right? So the release is very low stakes. >> >> Kenn >> >> On Fri, Jan 19, 2024 at 4:55 PM Robert Bradshaw via dev < >> dev@beam.apache.org> wrote: >> >>> Thanks. >>> >>> +1 >>> >>> >>> On Fri, Jan 19, 2024 at 1:24 PM Yi Hu wrote: >>> The process I have been following is [1]. I have also suggested edits to the voting email template to include the self-link. However, does anyone can edit this doc so the change can be made? Otherwise we might better to migrate this doc to https://github.com/apache/beam/tree/master/contributor-docs [1] https://s.apache.org/beam-release-vendored-artifacts On Thu, Jan 18, 2024 at 2:56 PM Robert Bradshaw via dev < dev@beam.apache.org> wrote: > Could you explain the process you used to produce these artifacts? > > On Thu, Jan 18, 2024 at 11:23 AM Kenneth Knowles > wrote: > >> +1 >> >> On Wed, Jan 17, 2024 at 6:03 PM Yi Hu via dev >> wrote: >> >>> Hi everyone, >>> >>> >>> Please review the release of the following artifacts that we vendor: >>> >>> * beam-vendor-grpc-1_60_1 >>> >>> >>> Please review and vote on the release candidate #1 for the version >>> 0.1, as follows: >>> >>> [ ] +1, Approve the release >>> >>> [ ] -1, Do not approve the release (please provide specific comments) >>> >>> >>> The complete staging area is available for your review, which >>> includes: >>> >>> * the official Apache source release to be deployed to >>> dist.apache.org [1], which is signed with the key with fingerprint >>> 8935B943A188DE65 [2], >>> >>> * all artifacts to be deployed to the Maven Central Repository [3], >>> >>> * commit hash "52b4a9cb58e486745ded7d53a5b6e2d2312e9551" [4], >>> >>> The vote will be open for at least 72 hours. It is adopted by >>> majority approval, with at least 3 PMC affirmative votes. >>> >>> Thanks, >>> >>> Release Manager >>> >>> [1] https://dist.apache.org/repos/dist/dev/beam/vendor/ >>> >>> [2] https://dist.apache.org/repos/dist/release/beam/KEYS >>> >>> [3] >>> https://repository.apache.org/content/repositories/orgapachebeam-1366/ >>> >>> [4] >>> https://github.com/apache/beam/commits/52b4a9cb58e486745ded7d53a5b6e2d2312e9551/ >>> >>> >>> -- >>> >>> Yi Hu, (he/him/his) >>> >>> Software Engineer >>> >>> >>>
Re: [VOTE] Vendored Dependencies Release
> Notably, the vendored artifact has no impact on the repo until the version used is also bumped. That is correct. The PR that actually bump the version then the change takes effect will be like https://github.com/apache/beam/pull/29976 On Mon, Jan 22, 2024 at 10:11 AM Kenneth Knowles wrote: > Notably, the vendored artifact has no impact on the repo until the version > used is also bumped, right? So the release is very low stakes. > > Kenn > > On Fri, Jan 19, 2024 at 4:55 PM Robert Bradshaw via dev < > dev@beam.apache.org> wrote: > >> Thanks. >> >> +1 >> >> >> On Fri, Jan 19, 2024 at 1:24 PM Yi Hu wrote: >> >>> The process I have been following is [1]. I have also suggested edits to >>> the voting email template to include the self-link. However, does anyone >>> can edit this doc so the change can be made? Otherwise we might better to >>> migrate this doc to >>> https://github.com/apache/beam/tree/master/contributor-docs >>> >>> [1] https://s.apache.org/beam-release-vendored-artifacts >>> >>> On Thu, Jan 18, 2024 at 2:56 PM Robert Bradshaw via dev < >>> dev@beam.apache.org> wrote: >>> Could you explain the process you used to produce these artifacts? On Thu, Jan 18, 2024 at 11:23 AM Kenneth Knowles wrote: > +1 > > On Wed, Jan 17, 2024 at 6:03 PM Yi Hu via dev > wrote: > >> Hi everyone, >> >> >> Please review the release of the following artifacts that we vendor: >> >> * beam-vendor-grpc-1_60_1 >> >> >> Please review and vote on the release candidate #1 for the version >> 0.1, as follows: >> >> [ ] +1, Approve the release >> >> [ ] -1, Do not approve the release (please provide specific comments) >> >> >> The complete staging area is available for your review, which >> includes: >> >> * the official Apache source release to be deployed to >> dist.apache.org [1], which is signed with the key with fingerprint >> 8935B943A188DE65 [2], >> >> * all artifacts to be deployed to the Maven Central Repository [3], >> >> * commit hash "52b4a9cb58e486745ded7d53a5b6e2d2312e9551" [4], >> >> The vote will be open for at least 72 hours. It is adopted by >> majority approval, with at least 3 PMC affirmative votes. >> >> Thanks, >> >> Release Manager >> >> [1] https://dist.apache.org/repos/dist/dev/beam/vendor/ >> >> [2] https://dist.apache.org/repos/dist/release/beam/KEYS >> >> [3] >> https://repository.apache.org/content/repositories/orgapachebeam-1366/ >> >> [4] >> https://github.com/apache/beam/commits/52b4a9cb58e486745ded7d53a5b6e2d2312e9551/ >> >> >> -- >> >> Yi Hu, (he/him/his) >> >> Software Engineer >> >> >>
Re: [VOTE] Vendored Dependencies Release
Notably, the vendored artifact has no impact on the repo until the version used is also bumped, right? So the release is very low stakes. Kenn On Fri, Jan 19, 2024 at 4:55 PM Robert Bradshaw via dev wrote: > Thanks. > > +1 > > > On Fri, Jan 19, 2024 at 1:24 PM Yi Hu wrote: > >> The process I have been following is [1]. I have also suggested edits to >> the voting email template to include the self-link. However, does anyone >> can edit this doc so the change can be made? Otherwise we might better to >> migrate this doc to >> https://github.com/apache/beam/tree/master/contributor-docs >> >> [1] https://s.apache.org/beam-release-vendored-artifacts >> >> On Thu, Jan 18, 2024 at 2:56 PM Robert Bradshaw via dev < >> dev@beam.apache.org> wrote: >> >>> Could you explain the process you used to produce these artifacts? >>> >>> On Thu, Jan 18, 2024 at 11:23 AM Kenneth Knowles >>> wrote: >>> +1 On Wed, Jan 17, 2024 at 6:03 PM Yi Hu via dev wrote: > Hi everyone, > > > Please review the release of the following artifacts that we vendor: > > * beam-vendor-grpc-1_60_1 > > > Please review and vote on the release candidate #1 for the version > 0.1, as follows: > > [ ] +1, Approve the release > > [ ] -1, Do not approve the release (please provide specific comments) > > > The complete staging area is available for your review, which includes: > > * the official Apache source release to be deployed to dist.apache.org > [1], which is signed with the key with fingerprint 8935B943A188DE65 [2], > > * all artifacts to be deployed to the Maven Central Repository [3], > > * commit hash "52b4a9cb58e486745ded7d53a5b6e2d2312e9551" [4], > > The vote will be open for at least 72 hours. It is adopted by majority > approval, with at least 3 PMC affirmative votes. > > Thanks, > > Release Manager > > [1] https://dist.apache.org/repos/dist/dev/beam/vendor/ > > [2] https://dist.apache.org/repos/dist/release/beam/KEYS > > [3] > https://repository.apache.org/content/repositories/orgapachebeam-1366/ > > [4] > https://github.com/apache/beam/commits/52b4a9cb58e486745ded7d53a5b6e2d2312e9551/ > > > -- > > Yi Hu, (he/him/his) > > Software Engineer > > >
Beam High Priority Issue Report (49)
This is your daily summary of Beam's current high priority issues that may need attention. See https://beam.apache.org/contribute/issue-priorities for the meaning and expectations around issue priorities. Unassigned P1 Issues: https://github.com/apache/beam/issues/29971 [Bug]: FixedWindows not working for large Kafka topic https://github.com/apache/beam/issues/29926 [Bug]: FileIO: lack of timeouts may cause the pipeline to get stuck indefinitely https://github.com/apache/beam/issues/29912 [Bug]: floatValueExtractor judge float and double equality directly https://github.com/apache/beam/issues/29902 [Bug]: Messages are not ACK on Pubsub starting Beam 2.52.0 on Flink Runner in detached mode https://github.com/apache/beam/issues/29413 [Bug]: Can not use Avro over 1.8.2 with Beam 2.52.0 https://github.com/apache/beam/issues/29099 [Bug]: FnAPI Java SDK Harness doesn't update user counters in OnTimer callback functions https://github.com/apache/beam/issues/29022 [Failing Test]: Python Github actions tests are failing due to update of pip https://github.com/apache/beam/issues/28760 [Bug]: EFO Kinesis IO reader provided by apache beam does not pick the event time for watermarking https://github.com/apache/beam/issues/28383 [Failing Test]: org.apache.beam.runners.dataflow.worker.StreamingDataflowWorkerTest.testMaxThreadMetric https://github.com/apache/beam/issues/28339 Fix failing "beam_PostCommit_XVR_GoUsingJava_Dataflow" job https://github.com/apache/beam/issues/28326 Bug: apache_beam.io.gcp.pubsublite.ReadFromPubSubLite not working https://github.com/apache/beam/issues/28142 [Bug]: [Go SDK] Memory seems to be leaking on 2.49.0 with Dataflow https://github.com/apache/beam/issues/27892 [Bug]: ignoreUnknownValues not working when using CreateDisposition.CREATE_IF_NEEDED https://github.com/apache/beam/issues/27648 [Bug]: Python SDFs (e.g. PeriodicImpulse) running in Flink and polling using tracker.defer_remainder have checkpoint size growing indefinitely https://github.com/apache/beam/issues/27616 [Bug]: Unable to use applyRowMutations() in bigquery IO apache beam java https://github.com/apache/beam/issues/27486 [Bug]: Read from datastore with inequality filters https://github.com/apache/beam/issues/27314 [Failing Test]: bigquery.StorageApiSinkCreateIfNeededIT.testCreateManyTables[1] https://github.com/apache/beam/issues/27238 [Bug]: Window trigger has lag when using Kafka and GroupByKey on Dataflow Runner https://github.com/apache/beam/issues/26911 [Bug]: UNNEST ARRAY with a nested ROW (described below) https://github.com/apache/beam/issues/26343 [Bug]: apache_beam.io.gcp.bigquery_read_it_test.ReadAllBQTests.test_read_queries is flaky https://github.com/apache/beam/issues/26329 [Bug]: BigQuerySourceBase does not propagate a Coder to AvroSource https://github.com/apache/beam/issues/26041 [Bug]: Unable to create exactly-once Flink pipeline with stream source and file sink https://github.com/apache/beam/issues/24776 [Bug]: Race condition in Python SDK Harness ProcessBundleProgress https://github.com/apache/beam/issues/24389 [Failing Test]: HadoopFormatIOElasticTest.classMethod ExceptionInInitializerError ContainerFetchException https://github.com/apache/beam/issues/24313 [Flaky]: apache_beam/runners/portability/portable_runner_test.py::PortableRunnerTestWithSubprocesses::test_pardo_state_with_custom_key_coder https://github.com/apache/beam/issues/23944 beam_PreCommit_Python_Cron regularily failing - test_pardo_large_input flaky https://github.com/apache/beam/issues/23709 [Flake]: Spark batch flakes in ParDoLifecycleTest.testTeardownCalledAfterExceptionInProcessElement and ParDoLifecycleTest.testTeardownCalledAfterExceptionInStartBundle https://github.com/apache/beam/issues/23525 [Bug]: Default PubsubMessage coder will drop message id and orderingKey https://github.com/apache/beam/issues/22913 [Bug]: beam_PostCommit_Java_ValidatesRunner_Flink is flakes in org.apache.beam.sdk.transforms.GroupByKeyTest$BasicTests.testAfterProcessingTimeContinuationTriggerUsingState https://github.com/apache/beam/issues/22605 [Bug]: Beam Python failure for dataflow_exercise_metrics_pipeline_test.ExerciseMetricsPipelineTest.test_metrics_it https://github.com/apache/beam/issues/21714 PulsarIOTest.testReadFromSimpleTopic is very flaky https://github.com/apache/beam/issues/21706 Flaky timeout in github Python unit test action StatefulDoFnOnDirectRunnerTest.test_dynamic_timer_clear_then_set_timer https://github.com/apache/beam/issues/21643 FnRunnerTest with non-trivial (order 1000 elements) numpy input flakes in non-cython environment https://github.com/apache/beam/issues/21476 WriteToBigQuery Dynamic table destinations returns wrong tableId https://github.com/apache/beam/issues/21469 beam_PostCommit_XVR_Flink flaky: Connection refused https://github.com/apache/beam/issues/21424 Java VR (Dataflow, V2, Streaming) failing: ParDoTest$TimestampTests/OnWindowExpirationTests
