There's a lot of value to switching to pytest even without xdist. Could we
prune back the goals of this first PR to just achieving feature parity with
nose, and make a followup PR for xdist?
-chad
On Mon, Oct 7, 2019 at 12:04 PM Udi Meiri wrote:
>
>
> On Fri, Oct 4, 2019 at 10:35 AM Chad
The Apache Beam team is pleased to announce the release of version 2.16.0.
Apache Beam is an open source unified programming model to define and
execute data processing pipelines, including ETL, batch and stream
(continuous) processing. See https://beam.apache.org
You can download the release
Thanks Pablo! Good to know. The rerunning worked great and the PR is merged
now.
On Mon, Oct 7, 2019 at 3:37 PM Pablo Estrada wrote:
> Hi Cyrus!
> Being stuck for the whole weekend is not normal. Sorry that you had to
> deal with that. I don't know why that happened - and yes, rerunning is a
>
Hi Cyrus!
Being stuck for the whole weekend is not normal. Sorry that you had to deal
with that. I don't know why that happened - and yes, rerunning is a good
thing to do.
In my experience, most jobs should take <2,3 hours to run. If it takes
longer, something is likely off with the testing infra.
We have some labels: easyfix, newbie, beginner, starter. Check them, and
let us know if they help you find an issue. If not, don't hesitate to ask -
I can try to look for a couple easier beginner contributions.
Best
-P.
On Mon, Oct 7, 2019 at 11:54 AM Leonardo Miguel <
I'm working on a docs PR[1] for the 2.16 release and the RAT precommit
check is stuck in the Jenkins queue (since Friday). Is it possible to move
this up, or is there a way to get an estimate for how long it will take
the precommit check to run?
[1] https://github.com/apache/beam/pull/9607
Best,
I was going to start with katas.
I have interest in the sdk-java and sdk-py, so maybe working on
examples-java and examples-py would be a start.
Em seg, 7 de out de 2019 às 15:30, Rui Wang escreveu:
> I am not aware of starter tags. Which component/project you are
> interested in?
>
>
> -Rui
>
I'm happy to announce that we have unanimously approved this release.
There are 8 approving votes, 5 of which are binding:
* Ahmet (al...@google.com)
* Pablo (pabl...@google.com)
* Robert (rober...@google.com)
* Kenneth (k...@apache.org)
* Jean-Baptiste (j...@nanthrax.net)
There are no
I am not aware of starter tags. Which component/project you are
interested in?
-Rui
On Mon, Oct 7, 2019 at 11:02 AM Leonardo Miguel <
leonardo.mig...@arquivei.com.br> wrote:
> Hi,
>
> I've been working with Beam for three years now and I would like to start
> contributing.
> Could someone
Hi,
I've been working with Beam for three years now and I would like to start
contributing.
Could someone please give me permission to assign issues to myself?
My jira username is leonardo.miguel
Do you have any Labels for begginers that I could start working on?
Thanks!
--
[]s
Leonardo
@Valentyn Tymofieiev You can use the
`--retain_docker_containers` pipeline option to avoid garbage collection.
On Mon, Oct 7, 2019 at 1:57 AM Maximilian Michels wrote:
> @Pablo Thanks for asking. Since the user is satisfied with the
> workaround for now, I feel better about the release. It's
Yes, Dataflow still uses the old API, for both counters and for its
progress/autoscaling mechanisms. We'd need to convert that over as
well (which is on the TODO list but lower than finishing up support
for portability in general).
On Mon, Oct 7, 2019 at 9:56 AM Robert Burke wrote:
>
> The Go
The Go SDK uses the old API [1], but it shouldn't be too hard to migrate it.
The main thing I'd want to do at the same time is move the dependencies on
the protos out of that package and have those live only in the harness
package [2]. I wasn't aware of that particular separation of concerns
On Fri, Oct 4, 2019 at 10:35 AM Chad Dombrova wrote:
>
> I have a WiP PR to convert Beam to use pytest, but it's been stalled.
>>
>
> What would it take to get it back on track?
>
Besides needing to convert ITs (removing save_main_session), which can be
split out to a later PR, there's
Works, thanks a lot!
P.
From: Kenneth Knowles
Sent: Monday, October 7, 2019 6:02 PM
To: dev
Subject: Re: Contributor permissions
Great. I have added you now. Try assigning the JIRA to yourself to confirm.
Kenn
On Mon, Oct 7, 2019 at 8:59 AM Paweł Kordek
Great. I have added you now. Try assigning the JIRA to yourself to confirm.
Kenn
On Mon, Oct 7, 2019 at 8:59 AM Paweł Kordek
wrote:
> Hi Kenneth
>
> Sorry, I forgot to include it in the email, the username is "pawel.kordek".
>
> Thanks
> Paweł
> --
> *From:* Kenneth
Hi Kenneth
Sorry, I forgot to include it in the email, the username is "pawel.kordek".
Thanks
Paweł
From: Kenneth Knowles
Sent: Monday, October 7, 2019 5:53 PM
To: dev
Subject: Re: Contributor permissions
Hi Paweł,
Welcome & thanks you for contributing!
Do
Hi Paweł,
Welcome & thanks you for contributing!
Do you have a JIRA account? I searched for your name and did not find
anything. If you tell me your Jira username I will add you to the
"Contributors" role so you can assign the JIRA to yourself.
Kenn
On Mon, Oct 7, 2019 at 8:43 AM Paweł Kordek
Hello
My name is Paweł and I since some time I'm working on PoC of Beam pipelines in
my company. I have been recently blocked by
https://issues.apache.org/jira/browse/BEAM-6860 and started digging a little
into it, finding some possible solutions, therefore I'd like to assign JIRA to
myself,
Welcome! That kind of feedback would be a huge contribution.
Kenn
On Mon, Oct 7, 2019 at 12:25 AM Ismaël Mejía wrote:
> Hello and welcome !
>
> You can now self assign Jira tickets. You don't need any additional
> permissions to open PRs.
> User/customer feedback is really appreciated so feel
Welcome Manuela!
The documentation on the Beam website [1] can help you too, in
particular to get some familiarity with the runtime part of Nexmark
(and the Java version of the queries). Maybe worth to try to run some
queries to see if your work environment is ok, and see how things work
and if
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
mock
2.0.0
3.0.5
2019-05-20
Hi Chad,
We're working on this. Sorry this is taking so long. Last time we hired
a company and we had the edited recordings the day after. This time, we
are going through a more manual process.
I'll check back about the progress.
Cheers,
Max
On 05.10.19 07:51, Chad Dombrova wrote:
Hi Max,
@Pablo Thanks for asking. Since the user is satisfied with the
workaround for now, I feel better about the release. It's also good to
stay on track with the release schedule.
@Ahmet/@Thomas Makes sense to go through the release manager, as it
prevents confusion around what is currently in the
Hello and welcome !
You can now self assign Jira tickets. You don't need any additional
permissions to open PRs.
User/customer feedback is really appreciated so feel free to bring more of that.
Cheers,
Ismaël
On Mon, Oct 7, 2019 at 7:58 AM Zoltán Kauker wrote:
>
> Dear All,
>
> I'm new to this
25 matches
Mail list logo
