Beam Dependency Check Report (2020-05-25)

ERROR: File 'src/build/dependencyUpdates/beam-dependency-check-report.html' does not exist

Re: Companies using Beam?

Oops, just saw you linked it earlier Aizhamal. Is it still open for input? On Mon, 25 May 2020 at 09:20, Matthias Baetens wrote: > I think this is a great idea. We could support the page with relevant > Meetup / Summit talks as well. > > Is there a place where we the website redesign is being

Re: What's the purpose of version=2.20.0-RC2 in gradle.properties?

Hi Jacek, The Gradle property is the source of truth for the Beam version. When we release the version, the RC suffix is dropped. The use of snapshot versions is normal during the development process. You probably want to work with the release artifacts, instead of cloning the development

Re: Try Beam Katas Today

Hi Austin, Thanks for your help in adding a new lesson. I will have a look and help to review the pull request. On your questions: 1. Apart from the *-remote-info.yaml, the other yaml files should contain Apache license header. We explicitly turn off license header check for the remote-info

DoFnSignature#isStateful deprecated

Hi, I have come across issue with multiple way of getting a meaningful flags for DoFns. We have  a) DoFnSignature#{usesState,usesTimers,isStateful,...}, and  b) DoFnSignatures#{usesState,usesTimers,isStateful,...} These two might not (and actually are not) aligned with each other. That can

Re: Companies using Beam?

I think this is a great idea. We could support the page with relevant Meetup / Summit talks as well. Is there a place where we the website redesign is being planned and where we can contribute ideas or discuss the structure of such a page? On Fri, 1 May 2020 at 20:00, Aizhamal Nurmamat kyzy

Contributor access to Beam JIRA

I'd like to work on some issues, assign issues to myself, and help close out old issues that are already resolved. Could you give me contributor access to the Beam JIRA?

Re: Try Beam Katas Today

Hi Henry, Cool. Most makes sense. What I am missing is the need for the '*-remote-info.yaml' in the beam repo (I do get what purpose it serves for Stepik). There is probably a good reason. To get nitpicky (am genuinely curious) --> It seems that this sort of metadata would get (re-)created

Re: 2.22.0 Release Update

I tried to validate the release branch on dataflow, but it looks like there's no tag yet for the 2.22 docker containers [1] I'm also fairly concerned with the artifact staging regressions introduced in BEAM-9383 [2] [1]

Re: Try Beam Katas Today

Hi Austin, The remote-info yaml files would get updated upon updating the course on Stepik, not entirely recreated as if from scratch. The important IDs metadata that track the course ID, section ID, lesson ID, and task ID are preserved. Having these files in the repo allows multiple people to be

Re: Try Beam Katas Today

Cool; thanks Henry! On Mon, May 25, 2020 at 7:49 PM Henry Suryawirawan wrote: > Hi Austin, > > The remote-info yaml files would get updated upon updating the course on > Stepik, not entirely recreated as if from scratch. > The important IDs metadata that track the course ID, section ID, lesson