The content does strike me as a dashboard snapshot more than something for
the list.

Really, it feels like something we could have as a badge link on the main
repo page, to see the latest results, instead of sending an email.

The trick there is visibility. If we have a way to kick the results
generation on demand, it should probably be documented somewhere related.



On Thu, Feb 6, 2025, 9:17 AM Ahmet Altay via dev <dev@beam.apache.org>
wrote:

> I think these emails clutter the dev list. Not really a big problem, those
> could be easily filtered out. I think for newcomers, this list might easily
> look like a list for machine generated emails rather than a place for
> discussion.
>
> On Thu, Feb 6, 2025 at 7:20 AM Kenneth Knowles <k...@apache.org> wrote:
>
>> I did use them for some time but now I am not. They are too frequent, and
>> I think we have more high priority issues than we have bandwidth to take
>> action on.
>>
>> I think getting an alert when a new high priority issue comes in is
>> valuable. If we could pare this down so that it was truly an alert rather
>> than a summary, I would pay attention.
>>
>
> I agree.
>
>
>>
>> Kenn
>>
>> On Wed, Feb 5, 2025 at 6:59 PM Ahmet Altay via dev <dev@beam.apache.org>
>> wrote:
>>
>>> Curiosity question: Is anyone using this email report or the beam
>>> metrics email?
>>>
>>> On Wed, Feb 5, 2025 at 2:02 AM <beamacti...@gmail.com> wrote:
>>>
>>>> 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/33859 The PostCommit Java
>>>> ValidatesRunner ULR job is flaky
>>>> https://github.com/apache/beam/issues/33854 [Failing Test]:
>>>> AttributeError for MaybeReshuffle in Python SDK
>>>> https://github.com/apache/beam/issues/33853 [Failing Test]: Namespace
>>>> error for prism_runner in Python STD
>>>> https://github.com/apache/beam/issues/33852 [Failing Test]: ValueError
>>>> in yaml for Python SDK
>>>> https://github.com/apache/beam/issues/33851 [Failing Test]:
>>>> portable_runner_test in Python SDK
>>>> https://github.com/apache/beam/issues/33834 The Republish Released
>>>> Docker Images job is flaky
>>>> https://github.com/apache/beam/issues/33698 The finalize_release job
>>>> is flaky
>>>> https://github.com/apache/beam/issues/33407 [Bug]: tfrecordio does not
>>>> work with snappy >= 0.7
>>>> https://github.com/apache/beam/issues/32997 [Bug]: Non Retained
>>>> Messages missing after MqttIO.Read checkpoint restore
>>>> https://github.com/apache/beam/issues/32509 [Bug]: Unable to Restart
>>>> Google Spanner Change Streams Consumer due to tableExists(table_name) bug
>>>> https://github.com/apache/beam/issues/31254 [Failing Test]: Onnx
>>>> inference unit tests are failing.
>>>> https://github.com/apache/beam/issues/29971 [Bug]: FixedWindows not
>>>> working for large Kafka topic
>>>> https://github.com/apache/beam/issues/29515 [Bug]: WriteToFiles in
>>>> python leave few records in temp directory when writing to large number
>>>> (100+) of files
>>>> 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/28760 [Bug]: EFO Kinesis IO
>>>> reader provided by apache beam does not pick the event time for 
>>>> watermarking
>>>> 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/25946 [Task]: Support more Beam
>>>> portable schema types as Python types
>>>> https://github.com/apache/beam/issues/24776 [Bug]: Race condition in
>>>> Python SDK Harness ProcessBundleProgress
>>>> https://github.com/apache/beam/issues/23525 [Bug]: Default
>>>> PubsubMessage coder will drop message id and orderingKey
>>>> 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/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/21260 Python DirectRunner does
>>>> not emit data at GC time
>>>> https://github.com/apache/beam/issues/20108 Python direct runner
>>>> doesn't emit empty pane when it should
>>>>
>>>>
>>>> P1 Issues with no update in the last week:
>>>>
>>>> https://github.com/apache/beam/issues/33744 [Flaky Py SDK Snapshots]:
>>>> Publish Beam SDK Snapshots is failing for Python distroless container
>>>> https://github.com/apache/beam/issues/33065 The Python
>>>> ValidatesContainer Dataflow ARM job is flaky
>>>> https://github.com/apache/beam/issues/31931 The IcebergIO Integration
>>>> Tests job is flaky
>>>> https://github.com/apache/beam/issues/30507 The LoadTests Go GBK Flink
>>>> Batch job is flaky
>>>> https://github.com/apache/beam/issues/30502 The LoadTests Go CoGBK
>>>> Flink Batch job is flaky
>>>> https://github.com/apache/beam/issues/25975 [Bug]: KinesisIO
>>>> processing-time watermarking can cause data loss
>>>>
>>>>
>>>>

Reply via email to