Re: Greetings from Tyson

Welcome, Tyson! On Wed, Apr 29, 2020 at 3:15 PM Rui Wang wrote: > Welcome! > > -Rui > > On Wed, Apr 29, 2020, 3:13 PM Brian Hulette wrote: > >> Welcome Tyson! >> >> On Wed, Apr 29, 2020 at 2:54 PM Ahmet Altay wrote: >> >>> Welcome! >>> >>> On Tue, Apr 28, 2020 at 3:06 PM Hannah Jiang >>> wrot

Re: No space left on device - beam-jenkins 1 and 7

builds&sa=D> https://builds.apache.org/computer/apache-beam-jenkins-15/builds <https://www.google.com/url?q=https://builds.apache.org/computer/apache-beam-jenkins-15/builds&sa=D> https://builds.apache.org/computer/apache-beam-jenkins-16/builds <https://www.google.com/url?q=htt

Re: Jenkins problems: javaPreCommitPortabilityApiJava11 and No Space left

The disk on jenkins5 was 100% full. I deleted some /tmp files owned by jenkins > 3d old, bringing it down to 90%. There a are still quite a few large files in the jenkins workspaces. I can look into ways to keep this cleaned up. On Wed, Feb 26, 2020 at 5:38 PM Kyle Weaver wrote: > It looks like

Re: Github flaky?

There is an active incident, from https://www.githubstatus.com/ On Tue, Feb 25, 2020 at 10:10 AM Luke Cwik wrote: > I have been getting errors from the Github UI when attempting to post a > comment / merge a commit / 500 errors when reloading a page. Anyone else > seeing this? >

Re: [ANNOUNCE] New committer: Hannah Jiang

Congrats, Hannah On Tue, Jan 28, 2020 at 4:46 PM Connell O'Callaghan wrote: > Thank you for sharing Luke!!! > > Well done and congratulations Hannah!! > > On Tue, Jan 28, 2020 at 4:45 PM Heejong Lee wrote: > >> Congratulations! :) >> >> On Tue, Jan 28, 2020 at 4:43 PM Yichi Zhang wrote: >>

Re: Jenkins jobs not running for my PR 10438

Oh, the PR 9903 run is quite old; I don't see a recent one yet. On Thu, Jan 2, 2020 at 2:48 PM Alan Myrvold wrote: > For PR 10427, I see > https://builds.apache.org/job/beam_PreCommit_Java_Phrase/1593/ > For PR 9903, I see > https://builds.apache.org/job/beam_PostCommit_Java_Ne

Re: Jenkins jobs not running for my PR 10438

For PR 10427, I see https://builds.apache.org/job/beam_PreCommit_Java_Phrase/1593/ For PR 9903, I see https://builds.apache.org/job/beam_PostCommit_Java_Nexmark_Flink_PR/22/ Maybe the PR status is not being updated when the jobs run? On Thu, Jan 2, 2020 at 2:37 PM Kai Jiang wrote: > same for h

Re: Beam Testing Tools FAQ

Nice, thanks! On Tue, Nov 26, 2019 at 8:04 AM Robert Bradshaw wrote: > Thanks! > > On Tue, Nov 26, 2019 at 7:43 AM Łukasz Gajowy wrote: > > > > Hi all, > > > > our documentation (either confluence or the website docs) describes how > to create various integration and performance tests - there a

Re: [ANNOUNCE] New committer: Brian Hulette

Congratulations, Brian! On Fri, Nov 15, 2019 at 11:11 AM Yifan Zou wrote: > Well deserved. Congratulations! > > On Fri, Nov 15, 2019 at 11:06 AM Kirill Kozlov > wrote: > >> Congratulations, Brian! >> >> On Fri, Nov 15, 2019 at 10:56 AM Udi Meiri wrote: >> >>> Congrats Brian! >>> >>> >>> On Fri

Re: Jenkins workflow improvement question

It would be a nice improvement, provided (as Luke pointed out) the same functionality exists for triggering jobs on pull request, review comment, postcommit, or cron and filtering jobs based on paths of files modified. On Tue, Nov 5, 2019 at 3:49 PM Luke Cwik wrote: > This would be great. > > I

Re: How to use a locally built worker image?

Yes, using the latest tag is problematic and can lead to unexpected behavior. Using a date/time or 2.17.0.dev-$USER tag would be better. The validates container shell script uses a datetime

Re: [ANNOUNCE] New committer: Alan Myrvold

Fri, Sep 27, 2019 at 11:17 AM Yichi Zhang < >>>>>>>>>>>>>> zyi...@google.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Congrats, Alan! >>>>>>>

Re: [PROPOSAL] Preparing for Beam 2.16.0 release

+1 Thanks for keeping to the schedule, Mark. On Thu, Aug 29, 2019 at 6:21 PM jincheng sun wrote: > Hi Mark, > > +1 and thank you for keeping the cadence! > > BTW I have mark the Fix Version for some of issues to 2.17, which can not > be merged into 2.16. > > Best, > Jincheng > > Mark Liu 于2019年

Re: [ANNOUNCE] Beam 2.14.0 Released!

Thanks for the release work, Anton! On Fri, Aug 2, 2019 at 9:08 AM Hannah Jiang wrote: > Thanks Anton for all the work to release it. > > On Fri, Aug 2, 2019 at 7:12 AM Connell O'Callaghan > wrote: > >> Well done Anton and all involved!!! >> >> On Fri, Aug 2, 2019 at 06:56 Robert Bradshaw wrot

Re: Proposal: Add permanent url to community metrics dashboard

Are all of the CVE issues fixed at the version in use? https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=grafana XSS isn't much of a concern until there is a hostname associated. On Wed, Jul 17, 2019 at 2:17 PM Pablo Estrada wrote: > I'd like to move this forward. Mikhail, would you be interested

Re: [PROPOSAL] Preparing for Beam 2.15.0 release

+1 Thanks for keeping the release cadence going. I like to see regular releases happening. On Wed, Jul 17, 2019 at 11:01 AM Yifan Zou wrote: > Hello Beam community! > > Beam 2.15 release branch cut date is July 31 according to the release > calendar [1]. I would like to volunteer myself to do th

Re: [ANNOUNCE] New committer: Robert Burke

Congrats, Robert! On Tue, Jul 16, 2019 at 11:46 AM Ismaël Mejía wrote: > Congrats Robert! > > > On Tue, Jul 16, 2019 at 8:19 PM Yichi Zhang wrote: > > > > Congratulations! > > > > On Tue, Jul 16, 2019 at 10:51 AM Holden Karau > wrote: > >> > >> Congratulations! :) > >> > >> On Tue, Jul 16, 201

Re: Beam local website development environment

You can serve (or test) the website locally, using https://cwiki.apache.org/confluence/display/BEAM/Website+Tips On Tue, Jun 11, 2019 at 3:27 PM Rakesh Kumar wrote: > Hi, > > I have been updating the documentation section of Beam website, mostly the > code examples [1], & [2]. I want to check th

Re: [ANNOUNCE] New PMC Member: Pablo Estrada

Congrats, Pablo! *From: *Robin Qiu *Date: *Wed, May 15, 2019 at 10:44 AM *To: * Congratulations, Pablo!! > > On Wed, May 15, 2019 at 10:43 AM Pablo Estrada wrote: > >> Thanks everyone for the encouragement, and thanks to the PMC for the >> recognition. I am honored and grateful. :) >> Best >>

Re: All validates runner tests seems to be broken.

s right after that >> finishes. Then do "Run Seed Job" after they all start on head again to >> restore the config. >> >> Andrew >> >> *From: *Alan Myrvold >> *Date: *Tue, May 14, 2019 at 1:59 PM >> *To: * >> >> That is a typo ad

Re: All validates runner tests seems to be broken.

That is a typo added in https://github.com/apache/beam/pull/8194 https://github.com/apache/beam/commit/1e7ea0da5073566c3fa26dbc1105105fbe6043ae#diff-9591f0d06e82e711681fd77ed287578b *From: *Ankur Goenka *Date: *Tue, May 14, 2019 at 1:43 PM *To: *dev Hi, > > Following tests seems to be broken bec

Re: Beam at Google Summer of Code 2019

Welcome, Tanay! Nice proposal. *From: *Kenneth Knowles *Date: *Mon, May 6, 2019 at 4:13 PM *To: *dev *Cc: * Nice! Welcome, Tanay! > > On Mon, May 6, 2019 at 3:56 PM Reza Rokni wrote: > >> +1 Congratulations! Looking forward to using your work ! >> >> *From: *Valentyn Tymofieiev >> *Date: *Tue

Re: Updates on Beam Jenkins

Thanks for this work, Yifan! On Mon, Apr 29, 2019 at 8:14 AM Ismaël Mejía wrote: > Thanks Yifan for all your work. Sometimes the work on infrastructure > is hidden, so it is great to acknowledge the importance of the > improvements you and the others have done. > > On Mon, Apr 29, 2019 at 5:11 P

Re: [Discuss] Publishing pre-release artifacts to repositories

Great idea. I like the RC candidates to follow as much as the release artifact process as possible. On Wed, Apr 24, 2019 at 3:27 PM Ahmet Altay wrote: > To clarify my proposal, I am proposing publishing to the production pypi > repository with an rc tag in the version. And in turn allow users to

Re: [ANNOUNCE] New committer announcement: Yifan Zou

Congrats, Yifan!!! On Mon, Apr 22, 2019 at 10:24 AM Robin Qiu wrote: > Congratulations Yifan! > > On Mon, Apr 22, 2019 at 10:17 AM Chamikara Jayalath > wrote: > >> Congrats Yifan! >> >> On Mon, Apr 22, 2019 at 10:02 AM Maximilian Michels >> wrote: >> >>> Congrats! Great work. >>> >>> -Max >>>

Re: New contributor to Beam

Welcome, Cyrus! On Wed, Apr 17, 2019 at 12:49 PM Ahmet Altay wrote: > Welcome! > > On Wed, Apr 17, 2019 at 12:26 PM Rose Nguyen wrote: > >> Welcome, Cyrus!! >> >> On Wed, Apr 17, 2019 at 11:58 AM Niklas Hansson < >> niklas.sven.hans...@gmail.com> wrote: >> >>> Welcome :) >>> >>> Den ons 17 apr.

Re: Removing :beam-website:testWebsite from gradle build target

+1 if possible, removing link checks would be nice too, if they are unreliable and there is a way to disable them. On Mon, Apr 1, 2019 at 10:33 AM Mikhail Gryzykhin wrote: > +1 on this. I'd prefer to have this as pre-commit only. > > On Mon, Apr 1, 2019 at 9:09 AM Andrew Pilloud wrote: > >> +1

Re: [ANNOUNCE] New committer announcement: Mark Liu

congratulations, Mark!!! On Mon, Mar 25, 2019 at 10:05 AM Ruoyun Huang wrote: > Congratulations Mark! > > On Mon, Mar 25, 2019 at 9:31 AM Udi Meiri wrote: > >> Congrats Mark! >> >> On Mon, Mar 25, 2019 at 9:24 AM Ahmet Altay wrote: >> >>> Congratulations, Mark! 🎉 >>> >>> On Mon, Mar 25, 2019 a

Re: Selectively running tests?

The includedRegions was set up as part of https://issues.apache.org/jira/browse/BEAM-4445 and there are additional paths added from https://github.com/apache/beam/blob/6bb4b2332b11bd8295ac6965be8426b9c38fa454/.test-infra/jenkins/PrecommitJobBuilder.groovy#L65 Not sure why they are not working, but

Re: [PROPOSAL] Prepare Beam 2.11.0 release

Thanks for volunteering. Glad to see the schedule being kept. On Fri, Feb 8, 2019 at 5:58 AM Maximilian Michels wrote: > +1 We should keep up the release cycle even though we are a bit late > with 2.10.0 > > On 08.02.19 02:10, Andrew Pilloud wrote: > > +1 let's keep things going. Thanks for volu

Re: Dealing with expensive jenkins + Dataflow jobs

Agreeing with Robert about "what is it we're trying to test?". Would a smaller performance test find the same issues, faster and more reliably? We have seen issues with the apache-beam-testing project exceeding quota during dataflow jobs, resulting in spurious failures during precommits and postco

Re: Master broken

The Jenkins test does a fresh clone of the repo, without generating code before the spotless test. On Fri, Jan 18, 2019 at 11:41 AM Kenneth Knowles wrote: > Those are the paths that cause the Jenkins job to be run. It doesn't > affect the Gradle task. > > Kenn > > On Fri, Jan 18, 2019 at 11:34 A

Re: Proposal: Portability SDKHarness Docker Image Release with Beam Version Release.

+1 This would be great. gcr.io seems like a good option for snapshots due to the permissions from jenkins to upload and ability to keep snapshots around. On Wed, Jan 16, 2019 at 6:51 PM Ruoyun Huang wrote: > +1 This would be a great thing to have. > > On Wed, Jan 16, 2019 at 6:11 PM Ankur Goenka

Re: [RFC] I made a new tabbed Beam view in Jenkins

2018 at 1:25 PM Alan Myrvold wrote: > >> It does look much better! >> >> On Tue, Dec 18, 2018 at 1:10 PM Ahmet Altay wrote: >> >>> I like this version, it looks cleaner than the current combined view. >>> >>> On Tue, Dec 18, 2018 at 12:53 PM Sco

Re: [RFC] I made a new tabbed Beam view in Jenkins

It does look much better! On Tue, Dec 18, 2018 at 1:10 PM Ahmet Altay wrote: > I like this version, it looks cleaner than the current combined view. > > On Tue, Dec 18, 2018 at 12:53 PM Scott Wegner wrote: > >> Very cool. I also didn't realize we had control over the Jenkins "views". >> >> We c

Re: INSTANCE_GROUP_MANAGERS quota limit exceeded

s-central1 ( the current quota >> is 100). >> >> Yifan >> >> On Fri, Nov 2, 2018 at 1:49 PM Alan Myrvold wrote: >> >>> Not sure, but I expect that each dataflow job needs a managed instance >>> group on the apache-beam-testing project, so it would

Re: INSTANCE_GROUP_MANAGERS quota limit exceeded

Not sure, but I expect that each dataflow job needs a managed instance group on the apache-beam-testing project, so it would depend on how many dataflow jobs are being run in parallel. The quota for concurrent dataflow jobs is 300, the quota for managed instance groups is 100. It would make sense t

Re: Never get spotless errors with this one weird trick

Thanks for the trick. I added it to https://cwiki.apache.org/confluence/display/BEAM/Java+Tips On Thu, Nov 1, 2018 at 2:26 PM Ankur Goenka wrote: > Thanks for sharing the trick. > > > On Thu, Nov 1, 2018 at 9:30 AM Kenneth Knowles wrote: > >> Hi all, >> >> Scott just separated the spotless chec

Re: Updated beam contribute page, development tips for languages in wiki

I like that change, especially providing all the resources in one spot. http://apache-beam-website-pull-requests.storage.googleapis.com/6912/contribute/get-help/index.html On Thu, Nov 1, 2018 at 11:13 AM Kenneth Knowles wrote: > To make it concrete and not just critique, I put together > https:/

Re: Updated beam contribute page, development tips for languages in wiki

/beam.apache.org/contribute/design-documents/ or a wiki page. >> >> Kenn >> >> On Thu, Nov 1, 2018 at 9:21 AM Alan Myrvold wrote: >> >>> Thanks to feedback from Sam when he got started with Beam, and helpful >>> suggestions from Thomas and Scott, the

Re: [ANNOUNCE] New committer announcement, Euphoria edition

Congrats! Euphoria for beam looks awesome. On Thu, Nov 1, 2018 at 9:49 AM Ahmet Altay wrote: > Congratulations! > > On Thu, Nov 1, 2018 at 9:36 AM, Tim wrote: > >> Congratulations and welcome! >> >> Tim >> >> On 1 Nov 2018, at 17:06, M

Updated beam contribute page, development tips for languages in wiki

Thanks to feedback from Sam when he got started with Beam, and helpful suggestions from Thomas and Scott, the beam contribute [1] page has been updated to hopefully make contributions easier, and the beam wiki

Re: Edit access to the Apache Beam Confluence Wiki?

Thanks! On Mon, Oct 29, 2018 at 2:57 PM Thomas Weise wrote: > You should be all set now. > > On Mon, Oct 29, 2018 at 1:49 PM Alan Myrvold wrote: > >> Can I get edit access to the Apache Beam Confluence Wiki, >> https://cwiki.apache.org/confluence/display/BEAM ? >>

Edit access to the Apache Beam Confluence Wiki?

Can I get edit access to the Apache Beam Confluence Wiki, https://cwiki.apache.org/confluence/display/BEAM ? I'd like to move some FAQ around contributing to the wiki. Thanks Alan

Re: Is it possible to be added to the apache beam testing group?

I've added you to the apache-beam-jenkins account. We try to limit the users with access and expect that the test results are debuggable. Once you find the issue, if there are any testability improvements to make, please let me know. On Fri, Oct 26, 2018 at 1:59 PM Alex Amato wrote: > I was tryi

New Edit button on beam.apache.org pages

To make small documentation changes easier, there is now an Edit button at the top right of the pages on https://beam.apache.org. This button opens the source .md file on the master branch of the beam repository in the github web editor. After making changes you can create a pull request to ask to

Re: python tests run as part of 'javaPreCommit'

Good idea on having a flag to make the test run without GCP credentials. I logged this as https://issues.apache.org/jira/browse/BEAM-5771 and can look into this, unless someone else prefers. On Tue, Oct 16, 2018 at 9:18 AM Scott Wegner wrote: > There was some discussion recently about ensuring a

Re: Modular IO presentation at Apachecon

Thanks for the slides. Really enjoyed the talk in person, especially the concept that IO is a transformation, and a source or sink are not special and the splittable DoFn explanation. On Wed, Sep 26, 2018 at 2:17 PM Ismaël Mejía wrote: > Hello, today Eugene and me did a talk about about modular

Re: [ANNOUNCEMENT] New Beam chair: Kenneth Knowles

Congrats, Kenn. On Wed, Sep 19, 2018 at 1:08 PM Maximilian Michels wrote: > Congrats! > > On 19.09.18 22:07, Robin Qiu wrote: > > Congratulations, Kenn! > > > > On Wed, Sep 19, 2018 at 1:05 PM Lukasz Cwik > > wrote: > > > > Congrats Kenn. > > > > On Wed, Sep 19,

Re: [VOTE] Donating the Dataflow Worker code to Apache Beam

+1 On Fri, Sep 14, 2018 at 3:16 PM Boyuan Zhang wrote: > +1 > > On Fri, Sep 14, 2018 at 3:15 PM Henning Rohde wrote: > >> +1 >> >> On Fri, Sep 14, 2018 at 2:40 PM Ahmet Altay wrote: >> >>> +1 (binding) >>> >>> On Fri, Sep 14, 2018 at 2:35 PM, Lukasz Cwik wrote: >>> +1 (binding)

Re: Should we allow ValidatesRunner tests to have access to file systems?

I think this should be an integration test if it requires more access than the current ValidatesRunner tests. Although the ValidatesRunner and integration tests are similar, the intent is that the validates runner tests are smaller and more like component tests, and there have been discusions on f

Re: [Proposal] Track non-code contributions in Jira

I like the idea of recognizing non-code contributions. These other efforts have been very helpful. On Thu, Aug 23, 2018 at 3:07 PM Griselda Cuevas wrote: > Hi Beam Community, > > I'd like to start tracking non-code contributions for Beam, specially > around these six categories: > 1) Project Man

Re: Policy for Python ValidatesRunner vs IT tests?

The ValidatesContainer test builds the python portable worker container using docker, pushes it, then runs a dataflow pipeline using the container with the flag --worker_harness_container_image. There is only one test that does this, and it is also an 'IT' test. On Tue, Aug 14, 2018 at 3:27 PM Pab

Re: Java precommit and postcommit tests are failing

://github.com/apache/beam/pull/6046 On Tue, Jul 24, 2018 at 9:21 AM Alan Myrvold wrote: > I can take a look at it today > > On Mon, Jul 23, 2018 at 10:32 PM Rui Wang wrote: > >> It is at least frequent (and event consistent) based on the list of >> failed

Re: Java precommit and postcommit tests are failing

I can take a look at it today On Mon, Jul 23, 2018 at 10:32 PM Rui Wang wrote: > It is at least frequent (and event consistent) based on the list of failed > PR which run java checks. > > > Also, this issue is being tracked by > https://issues.apache.org/jira/browse/BEAM-4847. > > > -Rui > > On

Re: [PROPOSAL] Prepare Beam 2.6.0 release

+1 Thanks for volunteering, Pablo On Wed, Jul 11, 2018 at 11:49 AM Jason Kuster wrote: > +1 sounds great > > On Wed, Jul 11, 2018 at 11:06 AM Thomas Weise wrote: > >> +1 >> >> Thanks for volunteering, Pablo! >> >> On Mon, Jul 9, 2018 at 9:56 PM Jean-Baptiste Onofré >> wrote: >> >>> +1 >>> >>>

Re: Broken seed job

The outage likely fixed it. I would have expected running the standalone job with the trigger phrase should have fixed it. Did it not? On Wed, Jul 11, 2018 at 8:45 AM Lukasz Cwik wrote: > I believe there was an outage a few hours ago. > > On Wed, Jul 11, 2018 at 8:36 AM Łukasz Gajowy > wrote: >

Proposal: Apache Beam Contributor Metrics: Collection, Display, Actions

I am proposing an html dashboard for some key contributor metrics, initially the weekly passing rate of post-commit tests and the speed of pre-commit tests, then expanding to code review and release metrics. https://s.apache.org/beam-contributor-metrics Comments welcome. Alan

Re: Auto closing stale PRs label

Glad to see it is working. The requests currently marked stale can be found with https://github.com/apache/beam/labels/stale On Tue, Jun 26, 2018 at 9:34 PM Rafael Fernandez wrote: > Neat! Thanks for showing me where the options are. > > On Tue, Jun 26, 2018 at 7:24 PM Kenneth Knowles wrote: >

Re: Going on leave for a bit

Congrats, Kenn and have a great break. On Tue, Jun 26, 2018 at 9:10 AM Alexey Romanenko wrote: > Best wishes to you and your family, Kenneth! > > Alexey > > On 26 Jun 2018, at 15:45, Rafael Fernandez wrote: > > Have a great time, Kenn! > > On Tue, Jun 26, 2018 at 5:49 AM Ismaël Mejía wrote: >

Re: [RESULT][VOTE] Apache Beam, version 2.5.0, release candidate #2

It would be a more predictable cadence to have a consistent timing between when the release branches are cut, and not when the release is published. If 2.5.0 was cut on June 5, then 2.6.0 could be cut July 17? On Mon, Jun 25, 2018 at 10:57 AM Ahmet Altay wrote: > > > On Mon, Jun 25, 2018 at 10:

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

:47 AM Ahmet Altay wrote: > > > > I already voted a +1 2 days ago. > > > > Again: > > > > +1 (binding) > > > > Thank you JB! > > > > On Fri, Jun 22, 2018 at 9:23 AM, Alan Myrvold > wrote: > >> > >> The > https:/

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

The https://dist.apache.org/repos/dist/dev/beam/2.5.0/apache-beam-2.5.0-source-release.zip still contains the beam-release-2.5.0/gradle/wrapper/gradle-wrapper.jar. Does that need to be removed before releasing it? On Fri, Jun 22, 2018 at 9:11 AM Reuven Lax wrote: > +1 (binding) > > On Fri, Jun 2

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #1

+1 (non-binding) tested some of the quickstarts On Sun, Jun 10, 2018 at 1:39 AM Tim wrote: > Tested by our team: > - mvn inclusion > - Avro, ES, Hadoop IF IO > - Pipelines run on Spark (Cloudera 5.12.0 YARN cluster) > - Reviewed release notes > > +1 > > Thanks also to everyone who helped get ov

Re: Announcement & Proposal: HDFS tests on large cluster.

(or other value). > @Alan Myrvold was already helpful with kubernetes cluster settings so > far, but I am not aware who made decisions regarding that as > this will increase monthly billing. > > Kamil Szewczyk > > 2018-06-07 6:27 GMT+02:00 Kenneth Knowles : > >> This is

Apache Beam Contribution Guide Improvements

estions in the document, https://docs.google.com/document/d/1zukoPXPgUq3Vli_rOJ0ykzK6NbR6g-FrgSHZjLd23bo/edit?usp=sharing Alan Myrvold

Re: [VOTE] Code Review Response-time SLO

Proposal 1: +1 Proposal 2: 0 Additional comments: Does this apply to committers only, or are contributors encourage to volunteer as an additional reviewer? I like the idea of documenting who is keen to review which area, plus reviewer availability. >From a contributor standpoint, it is worth avoid

Re: [VOTE] Use probot/stale to automatically manage stale pull requests

+1 (non-binding) I updated the pull request to be 60 days (instead of 90) to match the contribute policy. On Fri, Jun 1, 2018 at 9:21 AM Kenneth Knowles wrote: > Hi all, > > Following the discussion, please vote on the move to activate > probot/stale [3] to notify authors of stale PRs per curren

Re: Closing (automatically?) inactive pull requests

so let's do that now to make sure no > one missed this discussion. > > On Thu, May 31, 2018 at 9:33 PM Alan Myrvold wrote: > >> Thanks. I can look into adding the stale.yaml file for old pull requests/ >> >> On Thu, May 31, 2018 at 8:07 PM Kenneth Knowles

Re: Documenting Github PR jenkins trigger phrases

This is tracked by https://issues.apache.org/jira/browse/BEAM-3068 On Fri, Jun 1, 2018 at 7:38 AM Ismaël Mejía wrote: > Any progress on this ? Is there a JIRA to track it ? > On Fri, May 11, 2018 at 6:02 PM Jean-Baptiste Onofré > wrote: > > > > Agree, I thought there's already a PR about that.

Re: Closing (automatically?) inactive pull requests

ok the liberty of assigning > BEAM-4423 to you, in case throwing together the needed configs is fresh in > your mind and you are in the mood to continue. (if not, pass the hot > potato, back to me is OK too :-) > > Kenn > > On Thu, May 31, 2018 at 4:50 PM Alan Myrvold wrote:

Re: [ANNOUNCEMENT] New committers, May 2018 edition!

Congrats Gris+Pablo+Jason. Well deserved. On Thu, May 31, 2018 at 9:15 PM Jason Kuster wrote: > Thank you to Davor and the PMC; I'm excited to be able to help Beam in > this new capacity. Bring on the PRs. :D > > On Thu, May 31, 2018 at 8:55 PM Xin Wang wrote: > >> Congrats! >> >> - Xin Wang >>

Re: Closing (automatically?) inactive pull requests

INFRA-16589 got closed asking to clarify that the probot-stale app would not have permissions to merge automatically. >From my reading of the permissions documentation, it would not. I added a comment to INFRA-16589 On Tue, May 29, 2018 at 10:05 AM Lukasz Cwik wrote: > I opened up INFRA-16589 >

Re: Kubernetes cluster of apache-beam-testing project

found that used to download and install kubectl on beam-jenkins. > > https://github.com/apache/infrastructure-puppet/blob/95aed4f4f7cdce79a1f0fc8b1e581f13fedf63ff/modules/build_slaves/manifests/kube.pp > > On Thu, May 24, 2018 at 10:18 AM Alan Myrvold wrote: > >> I can up

Re: Kubernetes cluster of apache-beam-testing project

I can update the version of the io-datastores cluster master and node pools. I don't have access to the kubectl version on the executors ... I can ask around for that. On Wed, May 23, 2018 at 4:59 AM Kamil Szewczyk wrote: > Dear Beam Devs, > > we are using kubernetes to on demand create/tear do

Re: I'm back and ready to help grow our community!

Congratulations on graduating!!! Glad you're back. On Tue, May 22, 2018 at 3:01 AM Matthias Baetens wrote: > Same here - shame on me. Congratulations on the graduation Gris, very > happy to have you back! > > On Tue, 22 May 2018 at 09:19 Ismaël Mejía wrote: > >> I missed somehow this email thre

Re: [VOTE] Go SDK

+1 (non-binding) Nice work! On Tue, May 22, 2018 at 9:18 AM Pablo Estrada wrote: > +1 (binding) > Very excited to see this! > > On Tue, May 22, 2018 at 9:09 AM Thomas Weise wrote: > >> +1 and congrats! >> >> >> On Tue, May 22, 2018 at 8:48 AM, Rafael Fernandez >> wrote: >> >>> +1 ! >>> >>> On

Re: Jenkins Post Commit Status to Github

I saw ~1-2 hour latency for the trigger happening yesterday. Not sure what would cause it to stop or be slow. On Wed, May 9, 2018 at 10:45 AM Lukasz Cwik wrote: > It seems as though precommits are no longer triggering and trigger > requests like 'Run Java PreCommit' are no longer honored. > > On

Re: Beam parent SNAPSHOTs are not being built

t;>>>> 2.5.0-SNAPSHOT >>>>>>> >>>>>>> >>>>>>> >>>>>>> 4.0.0 >>>>>>> >>>>>>> >>>>>>> com.google.cloud >>>>>>> >>>>>&

Re: Beam parent SNAPSHOTs are not being built

5.0 blocker ? > > On Wed, Apr 25, 2018 at 2:05 PM Alan Myrvold wrote: > >> I think this corresponds with the move from maven to gradle snapshot >> releases. >> Issue logged as https://issues.apache.org/jira/browse/BEAM-4170 >> >> On Wed, Apr 25, 2018 at 1:57 PM Chami

Re: Beam parent SNAPSHOTs are not being built

I think this corresponds with the move from maven to gradle snapshot releases. Issue logged as https://issues.apache.org/jira/browse/BEAM-4170 On Wed, Apr 25, 2018 at 1:57 PM Chamikara Jayalath wrote: > Seems like we are not building some of the SNAPSHOT artifacts since > 4/9/2018. > For example

Re: [PROPOSAL] Preparing 2.5.0 release next week

We have been generating a maven project using the archetype from gradle built snapshot releases and running the quickstarts using maven. Are there other interesting tests to try that the quickstarts miss? On Thu, Apr 12, 2018 at 9:21 AM Kenneth Knowles wrote: > Just because I have probably miss

Re: Build failed in Jenkins: beam_SeedJob #1480

Typo in my pull request. Fixing it now. On Wed, Apr 11, 2018 at 11:42 AM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > -- > GitHub pull request #5101 of commit > 0a27a0

Re: Python postcommit and precommit

I think we should replace the shell script with a top level pythonPostCommit gradle target, similar to the precomment. On Mon, Apr 9, 2018 at 12:12 PM Lukasz Cwik wrote: > The shell scripts still exist instead of using Gradle. Migrating to Gradle > as the build system hasn't addressed this (only

Re: [ANNOUCEMENT] New Foundation members!

Congratulations! On Mon, Apr 2, 2018 at 9:14 AM Scott Wegner wrote: > Congrats! > > On Sat, Mar 31, 2018 at 12:18 PM Robert Burke wrote: > >> Congratulations! >> >> On Sat, 31 Mar 2018 at 11:53 Ekrem Aksoy wrote: >> >>> Congrats! >>> >>> On Sat, Mar 31, 2018 at 2:08 AM, Davor Bonaci wrote: >>

Re: Build breaks on examples on jenkins with dataflow runner

Thomas logged this issue as https://issues.apache.org/jira/projects/BEAM/issues/BEAM-3964 On Wed, Mar 28, 2018 at 10:09 AM Alan Myrvold wrote: > I looked at one failure, and saw this error in the log. Could it be > related to https://github.com/apache/beam/pull/4918 ? > > > 2

Re: Build breaks on examples on jenkins with dataflow runner

I looked at one failure, and saw this error in the log. Could it be related to https://github.com/apache/beam/pull/4918 ? 2018-03-28 09:45:26.603 PDTThread 25 died. Expand all | Collapse all { insertId: "776545081849523:822129:0:57106" jsonPayload: { exception: "java.lang.NoSuchMethodError: o

Apache Beam 2.4.0 release process retrospective and automation possibilities

Robert explained his experience with the release process as the release engineer for 2.4.0, and we discussed the prototype shell script for checking release progress in pull/4896 . I'd like to help automa

Re: Gradle status

I think the investment in gradle is worthwhile, and incrementally we will continue to make progress. From what I've seem, gradle is a good fit for this project and a path to a faster, more reliable build system. pull/4812 creates the release artifacts, al

Re: [VOTE] Release 2.4.0, release candidate #3

+1 I ran the java quickstarts against 2.4.0 and they passed. ./gradlew :release:runQuickstartsJava -Prepourl= https://repository.apache.org/content/repositories/orgapachebeam-1031 -Pver=2.4.0 On Mon, Mar 19, 2018 at 5:41 PM Ahmet Altay wrote: > I was able to run hourly_team_score. I was passing

New beam contributor experience?

There is a contribution guide at https://beam.apache.org/contribute/contribution-guide/ Has anyone had challenges / pain points when getting started with new contributions? Any suggestions for making this better? Alan

Re: [PROPOSITION] schedule some sanity tests on a daily basis

Great ideas. I want to see a daily signal for anything that could prevent a release from happening, and precommits that are fast and reliable for areas that are commonly broken by code changes. We are now running the java quickstarts daily on a cron schedule, using direct, dataflow, and local spar

Re: [VOTE] Release 2.4.0, release candidate #2

The dataflow java worker version wasn't updated on the branch as in past releases ... should it be? https://issues.apache.org/jira/browse/BEAM-3815 On Thu, Mar 8, 2018 at 1:40 PM Romain Manni-Bucau wrote: > Can still be provided as a generic one (like the an offset or key based > one) but good

Re: [VOTE] Release 2.4.0, release candidate #1

I don't see anything published to https://repository.apache.org/content/repositories/orgapachebeam-1028/ ? On Wed, Mar 7, 2018 at 9:26 AM Ahmet Altay wrote: > -1 for the same reason as Ismaël. Python version is not updated in the > release branch [1]. > > [1] > https://github.com/apache/beam/bl

Re: Merging Python code? Help avoid Python 3 regressions with these two simple steps :)

I ran "python3 --version" on each worker and all showed python 3.4.3. Is that too old? On Fri, Mar 2, 2018 at 10:04 AM Ahmet Altay wrote: > That is my understanding as well, it is requires attention from infra. > Could anyone help with this? I know we worked with infra before, what is > the bes

Re: Pain points in the 2.3.0 release / improvements to 2.4.0 release process?

d to pylib required manual action (like renaming the files) >>> >>> Thanks to the change I did on the assembly, the artifacts don't require >>> any >>> manual cleanup (whereas it was the case in previous release). >>> >>> Regards >>

Pain points in the 2.3.0 release / improvements to 2.4.0 release process?

Is there a list of pain points during the 2.3.0 release and improvements that can be made to the 2.4.0 release process?

Re: [VOTE] Release 2.3.0, release candidate #3

+1 Validated java quickstarts for direct, dataflow, apex, flink, and spark. On Wed, Feb 14, 2018 at 9:21 AM, Lukasz Cwik wrote: > +1 (binding) > Validated several quickstarts including the regression that I originally > reported with Spark. > > On Wed, Feb 14, 2018 at 5:34 AM, Ismaël Mejía wrot

Re: [VOTE] Release 2.3.0, release candidate #1

or in a dependency/related >> project ? >> >> I mean: is it something we have to fix/change in Beam ? >> >> Just curious as I'm not sure what you mean by "worker images" ;) >> >> Thanks ! >> Regards >> JB >>

Re: [VOTE] Release 2.3.0, release candidate #1

-1 (for now, hope to change this) Dataflow runner jobs are failing for me with 2.3.0 RC1, for both Java and Python. This is not an issues with the 2.3.0 RC1 SDK, we (google) need to release worker images. I have assigned these bugs to myself, and will be working to help get these workers release

  1   2   >