Anyone else have some time to help triage P0s and P1s? They should represent actual outages preventing the community from making progress, etc. And of course they are super urgent because of this.
Kenn On Thu, Aug 19, 2021 at 11:01 AM Beam Jira Bot <j...@apache.org> wrote: > This is your daily summary of Beam's current outages. See > https://beam.apache.org/contribute/jira-priorities/#p0-outage for the > meaning and expectations around P0 issues. > > BEAM-12766: Already Exists: Dataset > apache-beam-testing:python_bq_file_loads_NNN ( > https://issues.apache.org/jira/browse/BEAM-12766) > BEAM-12764: Can't get attribute 'new_block' on <module > 'pandas.core.internals.blocks' ( > https://issues.apache.org/jira/browse/BEAM-12764) > BEAM-12733: [beam_PostCommit_Java] > org.apache.beam.sdk.extensions.ml.RecommendationAIPredictIT.predict > failing (https://issues.apache.org/jira/browse/BEAM-12733) > BEAM-12694: DICOMIoIntegrationTest flaky due to store ID (Python > PreCommit) (https://issues.apache.org/jira/browse/BEAM-12694) > BEAM-12683: PythonPostCommits > RecommendationAIIT.test_create_catalog_item failing ( > https://issues.apache.org/jira/browse/BEAM-12683) >
