Re: Go error when building containers

It looks like the cached version of a package is stale and causing build errors when building beam. Chances are just deleting that /.gogradle directory will cause everything to rebuild from a clean state, so I'd try that. I think it should be /sdks/go/.gogradle On Thu, Jul 23, 2020 at 4:56 PM

Re: Go error when building containers

This is probably : https://issues.apache.org/jira/browse/BEAM-10567 On Thu, Jul 23, 2020 at 4:53 PM Brian Hulette wrote: > Whenever I build a container locally > (:sdks:java:container:docker, :sdks:python:container:py37:docker, ..) I get > a

Go error when building containers

Whenever I build a container locally (:sdks:java:container:docker, :sdks:python:container:py37:docker, ..) I get a Go error (log at the end of this message). I've discovered I can just comment out resolveBuildDependencies.dependsOn ":sdks:go:goBuild" in the relevant build.gradle file [1] whenever

Re: [BROKEN] Please add "Fix Version" when resolving or closing Jiras

+1 - I think I saw somewhere Resolved is intended for "this is fixed" while Closed is "the reporter/some authority has verified it's fixed". Doesn't seem to apply to us. On Thu, Jul 23, 2020 at 2:21 PM Kyle Weaver wrote: > > we could simplify those to a single state and let the Resolution field

Re: [BROKEN] Please add "Fix Version" when resolving or closing Jiras

> we could simplify those to a single state and let the Resolution field be the one source of truth for the nature of the resolution. +1 On Thu, Jul 23, 2020 at 2:14 PM Kenneth Knowles wrote: > This is unfortunate :-( > > Also unfortunate: I have just enough permissions to mess it up and not >

Re: Jenkins trigger phrase "run seed job" not working?

Oh, with our new Jenkins that's not an issue - I have admin access there, the issue is with checking old CI configuration, GitHub, infra stuff, etc. FYI, all PMC members as well have admin access to the new CI and can install plugins. This 'fetching committers during seed job' solution should not

Re: [BROKEN] Please add "Fix Version" when resolving or closing Jiras

This is unfortunate :-( Also unfortunate: I have just enough permissions to mess it up and not enough to fix it. You can follow https://issues.apache.org/jira/browse/INFRA-20563 By the way, does anyone really use the difference between "Resolved" and "Closed"? Since I am talking to Infra and

Re: Jenkins trigger phrase "run seed job" not working?

I have the same issue with Jenkins privileges. There's usually no insight to test triggering logic. For instance I happen to know that tests won't be started right now because Infra is restarting Jenkins to install a plugin, but that's only because I opened the ticket. I think fetching the list

Re: [VOTE] Make Apache Beam 2.24.0 the final release supporting Python 2.

+1 On Thu, Jul 23, 2020 at 1:15 PM Brian Hulette wrote: > +1 > > On Thu, Jul 23, 2020 at 1:05 PM Robert Bradshaw > wrote: > >> [X] +1: Remove Python 2 support in Apache Beam 2.25.0. >> >> According to our six-week release cadence, 2.24.0 (the last release to >> support Python 2) will be cut

Re: [VOTE] Make Apache Beam 2.24.0 the final release supporting Python 2.

[X] +1: Remove Python 2 support in Apache Beam 2.25.0. On Thu, Jul 23, 2020 at 1:05 PM Robert Bradshaw wrote: > [X] +1: Remove Python 2 support in Apache Beam 2.25.0. > > According to our six-week release cadence, 2.24.0 (the last release to > support Python 2) will be cut mid-August, and the

Re: [VOTE] Make Apache Beam 2.24.0 the final release supporting Python 2.

+1 On Thu, Jul 23, 2020 at 1:05 PM Robert Bradshaw wrote: > [X] +1: Remove Python 2 support in Apache Beam 2.25.0. > > According to our six-week release cadence, 2.24.0 (the last release to > support Python 2) will be cut mid-August, and the first release not > supporting Python 2 would be

Re: Jenkins trigger phrase "run seed job" not working?

Yes, I thought that whitelisting apache organization will do the trick, but apparently, it doesn't. Actually, it makes sense as we want to allow only beam committers and not all apache committers. I don't know the implications of membership in the apache github organization, but you for instance

Re: [VOTE] Make Apache Beam 2.24.0 the final release supporting Python 2.

[X] +1: Remove Python 2 support in Apache Beam 2.25.0. According to our six-week release cadence, 2.24.0 (the last release to support Python 2) will be cut mid-August, and the first release not supporting Python 2 would be expected to land sometime in October. This seems a reasonable timeline to

[VOTE] Make Apache Beam 2.24.0 the final release supporting Python 2.

Hi everyone, Please vote whether to make Apache Beam 2.24.0 the final release supporting Python 2 as follows. [ ] +1: Remove Python 2 support in Apache Beam 2.25.0. [ ] -1: Continue to support Python 2 in Apache Beam, and reconsider at a later date. The Beam community has pledged to sunset

Re: Python2.7 Beam End-of-Life Date

I have reviewed Slack, Twitter and User@ channels [1-3] we used to communicate our consideration to make 2.23.0 a final release supporting Py2. I did not see any objections or negative feedback there. I suggest we hold a VOTE to decide whether 2.24.0 should be the final release supporting Py2. I

Contributor permission for Beam Jira tickets

Hi, This is Varun from THG. I have created a couple of tickets related to improvements in Beam Java SDK. Could someone add me as a contributor for Beam's Jira issue tracker? I would like to assign tickets for my work. My JIRA id- varun.sharma Regards Varun Sharma

Re: ReadFromKafka returns error - RuntimeError: cannot encode a null byte[]

I tried enabling auto commit using flink and direct runners individually using the code below. Irrespective of environment-type ["DOCKER", "LOOPBACK"] for flink runner, the pipeline crashes with ERROR: java.lang.UnsupportedOperationException: The ActiveBundle does not have a registered bundle

Re: Python2.7 Beam End-of-Life Date

The release cut date for 2.24 is in a couple of weeks; if this is the last release supporting 2.7 we should make the call and announce it soon. On Mon, Jul 6, 2020 at 2:26 PM Robert Bradshaw wrote: > Note that just because Beam drops 2.x support in new releases doesn't > mean that the old

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

+1 (binding) I validated the hashes and signatures of all the release artifacts, and that the source tarball matches github at 5df6e7949629799c46d227171281364144149f5d. I also verified that the diff from the last RC contains what is expected and ran some basic pipelines against a Python 3 wheel

Re: Jenkins trigger phrase "run seed job" not working?

Thanks Damian! I saw that the config also has this: orgWhitelist(['apache']) Shouldn't that be enough to allow all Apache committers? I traced the code for the membership check here:

Re: Contributor permission for Beam Jira tickets

Done, added rworley as a contributor. Welcome. On Thu, Jul 23, 2020 at 9:29 AM Worley, Ryan wrote: > Hi, > > I have created BEAM-10564 and I would like to assign it to myself. Can > someone please add me as a contributor for Beam's Jira issue tracker? This > is the first of two pull requests

Re: [BROKEN] Please add "Fix Version" when resolving or closing Jiras

Yeah same for me. Not a huge deal.. I just noticed that the jira UI isn't rendering references to my closed tickets with a strikethrough, and I'd like to distinguish others as "won't fix" or "obsolete". It should be easy enough to backfill these once this is sorted out though. Brian On Thu, Jul

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

+1 (non-binding) Tested Java quickstart and an x-lang pipeline. Thanks, Cham On Wed, Jul 22, 2020 at 7:34 PM Ahmet Altay wrote: > +1 - I validated py3 quickstarts. > > On Wed, Jul 22, 2020 at 6:21 PM Valentyn Tymofieiev > wrote: > >> Hi everyone, >> >> Please review and vote on the release

Contributor permission for Beam Jira tickets

Hi, I have created BEAM-10564 and I would like to assign it to myself. Can someone please add me as a contributor for Beam's Jira issue tracker? This is the first of two pull requests that I plan to submit with minor improvements around working with Avro and BigQuery. Thanks, Ryan NOTICE:

Re: Jenkins trigger phrase "run seed job" not working?

Hi, You are right, the current behavior is wrong, I'm currently working to fix it asap. Our intention was to disable that only for non-committers. As a workaround, as a committer, you could manually add yourself (your GitHub username) to the whitelist of the SeedJob configuration:

Re: [BROKEN] Please add "Fix Version" when resolving or closing Jiras

I can close/resolve but it will show "Resolution: Unresolved": On 23.07.20 02:30, Brian Hulette wrote: Is setting the Resolution broken as well? I realized I've been closing jiras with Resolution "Unresolved" and I can't actually change it to "Fixed". On Tue, Jul 21, 2020 at 7:19 AM