Re: I did a quick investigation into xlang Expansion Service Auto-Startup for Beam devs.

2022-02-22 Thread Robert Burke
Well said Robert! I think that nuance: auto-searching for the dev jars, vs just printing out the command, was definitely lost on me! That seems like a pretty happy medium TBH. As long as one isn't copy pasting things from commands and directories, I'll be a happy camper. On Tue, Feb 22, 2022, 4:2

GKE Clusters Upgrade Question

2022-02-22 Thread Elias Segundo Antonio
Hi Apache Beam Team In order to keep our GKE Clusters up to date, Basic Auth is going to be disabled for the following clusters: * io-datastores * Metrics * Metrics-staging As you may know, OAuth is the current preferred method for authentication for both Google Cloud CLI and GKE. Prior to

ci-beam.a.o issues.

2022-02-22 Thread Chris Thistlethwaite
Greetings! I wanted to get folks on the same page when it comes to the latest issues with ci-beam.apache.org. There is a ticket open https://issues.apache.org/jira/browse/INFRA-22878 to track changes and troubleshooting. ASF Infra is working with Cloudbees to figure out any issues with Jenkins and

Re: I did a quick investigation into xlang Expansion Service Auto-Startup for Beam devs.

2022-02-22 Thread Robert Burke
Kerry, I think the next steps would be discussing if pivoting to using docker containers would be better than the current strategy of leaning on java jars, and not filing JIRAs with no clear tasks. As Daniel points out, the doc is the results of an investigation that may be useful for a future per

Flaky test issue report (51)

2022-02-22 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 determin

P1 issues report (72)

2022-02-22 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 https://beam.apache.

Re: [DISCUSS] Plugin classpaths

2022-02-22 Thread Matt Casters
It's a great idea for sure and I'll create a diagram for Beam and Hop separately. But ... this mail was mistakenly sent to the wrong dev group :-| Apologies for that. But while I'm on the topic, the Beam development model in general is simple in the sense that it forces a single classpath. When

[DISCUSS] Plugin classpaths

2022-02-22 Thread Matt Casters
Hello Hops, I've been struggling with a few classpath related issues: * Plugin data types are only accessible from the plugin they were introduced with (Avro, Graph) * It's not possible in a safe way for another plugin to add plugins (Beam) to the root class loader This has been causing all sort