High Priority Dependency Updates Of Beam Python SDK:
Dependency Name
Current Version
Latest Version
Release Date Of the Current Used Version
Release Date Of The Latest Release
cachetools
4.2.4
5.2.0
2021-12-27
2022-06-0
This is your daily summary of Beam's current P0 issues, not including flaky
tests.
See https://beam.apache.org/contribute/issue-priorities/#p0-outage for the
meaning and expectations around P0 issues.
https://api.github.com/repos/apache/beam/issues/21998: [Bug]: Loop last element
when wr
This is your daily summary of Beam's current P1 issues, not including flaky
tests.
See https://beam.apache.org/contribute/issue-priorities/#p1-critical for
the meaning and expectations around P1 issues.
https://api.github.com/repos/apache/beam/issues/22011: [Bug]:
org.apache.beam.sdk.io.
This is your daily summary of Beam's current flaky tests.
These are P1 issues because they have a major negative impact on the
community and make it hard to determine the quality of the software.
https://api.github.com/repos/apache/beam/issues/21714:
PulsarIOTest.testReadFromSimpleTopic i
Hello. I submitted a PR to fix a P1 issue but haven't gotten anyone to
review it yet. Would anyone be able to give some feedback or help out with
this issue? Thanks in advance.
https://github.com/apache/beam/pull/21786
*~Vincent*
Hi Elizaveta,
Very good question.
For this, I created
org.apache.beam.sdk.util.Preconditions.checkStateNotNull (
https://github.com/apache/beam/blob/1851eef15c5f455c95402ced50d757ea167d33d9/sdks/java/core/src/main/java/org/apache/beam/sdk/util/Preconditions.java#L450
)
Multiple reasons:
- Th
Hi folks,
I'm trying to provide some improvements for the beam pulsar connector.
Here are the very first two issues:
- async produce: https://github.com/apache/beam/issues/22025
- take auth params: https://github.com/apache/beam/issues/22027
PRs links are added into the issue also. Please take a
Forking thread because lots of people may just ignore this topic, per the
discussion :-)
(sometimes gmail doesn't fork thread properly, but here's hoping...)
I'll add some other outcomes of these emails:
- people file P0s that are not outages and P1s that are not data loss and
I downgrade them
Sounds good to me. Perhaps P0s > 36 hours ago (presumably they are more
like ~hours for true outages of CI/website/etc) and P1s > 7 days?
On Thu, Jun 23, 2022 at 1:27 PM Brian Hulette wrote:
> I think that Danny's alternate proposal (a daily email that show only
> issues last updated >7 days ago
Sounds good! It’s like our internal reports of JIRA tickets exceeding SLA
time and having no response from engineers. We either resolve them or
downgrade the priority to extend time window.
Besides,
1. P2 and P3 issues should be noticed and resolved as well. Shall we have a
longer time window for
10 matches
Mail list logo
