Re: Jira -> GitHub Issues Migration (This Friday)

2022-06-02 Thread Hector Miuler Malpica Gallegos
hahaha!!! excuse me, I'm thinking in the flink project when read the last email, I do not know why. *Hector Miuler Malpica Gallegos * El jue, 2 jun 2022 a la(s) 18:04, Danny McCormick (dannymccorm...@google.com) escribió: > Thanks for calling that out Hector - the

Re: Jira -> GitHub Issues Migration (This Friday)

2022-06-02 Thread Hector Miuler Malpica Gallegos
This migration includes the issues of the component `Kubernetes Operator` ? like this issue FLINK-27820 ? this issues correspond to the repository https://github.com/apache/flink-kubernetes-operator, keep it in mind. *Hector Miuler Malpica

P1 issues report (76)

2022-06-02 Thread Beam Jira Bot
This is your daily summary of Beam's current P1 issues, not including flaky tests (https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20priority%20%3D%20P1%20AND%20(labels%20is%20EMPTY%20OR%20labels%20!%3D%20flake). See

P0 (outage) report

2022-06-02 Thread Beam Jira Bot
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-14548: Jenkins job beam_SeedJob keeps failing (https://issues.apache.org/jira/browse/BEAM-14548)

Flaky test issue report (59)

2022-06-02 Thread Beam Jira Bot
This is your daily summary of Beam's current flaky tests (https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20labels%20%3D%20flake) These are P1 issues because they have a major negative impact on the community and make it hard to

Re: Failing beam_SeedJob

2022-06-02 Thread Kenneth Knowles
Commented on the Jira. Seems like it happens somewhat rarely, but is sometimes resolved by a restart, and sometimes has to do with some version mismatch issues. I did not find anything like a real root cause, just trial-and-error fixes. I'm not certain what may have occurred around May 19 to this

Beam Dependency Check Report (2022-05-18)

2022-06-02 Thread Apache Jenkins Server
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 JIRA Issue cachetools 4.2.4 5.2.0 2021-12-27

[CDAP IO] CDAP connector code reviews

2022-06-02 Thread Elizaveta Lomteva
Hi everyone! Our team is working on SparkReceiverIO as a part of Cdap IO connector project and we've prepared Add ReceiverBuilder for SparkReceiverIO PR [1]. This PR is ready for review. It would be great if you could take the time to share your thoughts and comments in the PR. Thank you in

Re: Jira -> GitHub Issues Migration (This Friday)

2022-06-02 Thread Alexey Romanenko
+1 That would be very helpful for mapping! > On 2 Jun 2022, at 17:48, Ahmet Altay wrote: > > Is it possible to add comments on the JIRAs with a link to the new > corresponding github issue? > > On Thu, Jun 2, 2022 at 8:47 AM Danny McCormick > wrote: > Thanks

Re: Failing beam_SeedJob

2022-06-02 Thread Alexey Romanenko
Thanks Ahmet and Ryan for taking a look! I agree that referenced commits seems are not related, that us why I was puzzled with this. > On 2 Jun 2022, at 17:56, Ahmet Altay wrote: > > > > On Thu, Jun 2, 2022 at 8:53 AM Ryan Thompson > wrote: > I asked in the

[Bug] Upgrading from Beam 2.34.0 to 2.39.0 breaks an application using bc-fips jar libraries

2022-06-02 Thread Manuel Yepez
Hello, We have an application that needs to remain FIPS compliant and so we have bc-fips-1.0.2.1.jar in our classpath. Up until now we used Beam 2.34.0 without any issue, but we are doing some upgrades to comply with security issues. However we detected that Beam 2.39.0 added other BC jars which

Re: Failing beam_SeedJob

2022-06-02 Thread Alexey Romanenko
I created a jira for this (not sure if it’s P0, but P1 for sure): https://issues.apache.org/jira/browse/BEAM-14548 Could someone, who has more knowledge than me in Beam infrastructure/Jenkins, take a look, please? — Alexey > On 31 May 2022,