+1 (binding)
On Mon, Mar 8, 2021 at 3:21 PM Pablo Estrada wrote:
> +1 (binding) verified signature
>
> On Mon, Mar 8, 2021 at 12:05 PM Kai Jiang wrote:
>
>> +1 (non-binding)
>>
>> On Mon, Mar 8, 2021 at 11:37 AM Andrew Pilloud
>> wrote:
>>
>>> Hi everyone,
>>> Please review and vote on the
+1 (binding) verified signature
On Mon, Mar 8, 2021 at 12:05 PM Kai Jiang wrote:
> +1 (non-binding)
>
> On Mon, Mar 8, 2021 at 11:37 AM Andrew Pilloud
> wrote:
>
>> Hi everyone,
>> Please review and vote on the release candidate #1 for
>> beam-vendor-calcite-1_26_0 version 0.1, as follows:
>>
Hi Fernando! I've added you as contributor to the Beam JIRA.
Welcome
-P.
On Mon, Mar 8, 2021 at 2:49 PM Fernando Morales Martinez <
fernando.mora...@wizeline.com> wrote:
> Hi team,
> Is this the right channel to add user ´thiscensustaker´to the Apache Beam
> contributor list?
>
> Thanks!
>
> -
Hi team,
Is this the right channel to add user ´thiscensustaker´to the Apache Beam
contributor list?
Thanks!
- Fernando Morales
--
*This email and its contents (including any attachments) are being sent to
you on the condition of confidentiality and may be protected by legal
privilege. Access
Here's the INFRA ticket I filed:
https://issues.apache.org/jira/browse/INFRA-17756
It is pretty easy to use the Jira feature.
Kenn
On Fri, Mar 5, 2021 at 11:55 AM Brian Hulette wrote:
> Kenn said he set this up via "Project Automation" in the Beam project page
> [1]. There seems to have been
Thanks. I created https://issues.apache.org/jira/browse/BEAM-11938 for
tracking this.
BTW are you able to reproduce this with the Kafka Taxi [1] example or did
it only occur with a different pipeline ?
If you can add any information that can be used to reproduce this to the
JIRA that will be
The fix PR https://github.com/apache/beam/pull/14148 which upgrades the
error prone version to 2.3.4 with failing checks disabled seems to be
working fine and is merged.
Please sync to head and try again.
On Mon, Mar 8, 2021 at 8:26 AM Daniel Collins wrote:
> Hello all,
>
> Can we make
+1 (non-binding)
On Mon, Mar 8, 2021 at 11:37 AM Andrew Pilloud wrote:
> Hi everyone,
> Please review and vote on the release candidate #1 for
> beam-vendor-calcite-1_26_0 version 0.1, as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific
Hi everyone,
Please review and vote on the release candidate #1 for
beam-vendor-calcite-1_26_0 version 0.1, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
Reviewers are encouraged to test their own use cases with the release
Hi Cham,
Complete stack trace can be accessed at
https://gist.github.com/amit5148/fcf3eea068020283b2c1ef04b57d493b
Regards,
Amit
On 2021/03/04 17:15:06, Chamikara Jayalath wrote:
> I haven't been able to reproduce this. Do you have a stack trace ?
>
> Thanks,
> Cham
>
> On Thu, Mar 4, 2021
Thank you for your response. Looking forward to the fix.
On Mon, Mar 8, 2021 at 2:16 AM Reuven Lax wrote:
> That test was added by mistake - it was originally added for debugging
> (all it did was run forever and print its results to the log), and I didn't
> mean to submit it with the PR. I'll
Hello all,
Can we make progress on either updating the version or rolling back
https://github.com/apache/beam/commit/dfeda2ab1dbebd8446766fae0cafb314ec29920f?
This is blocking any and all PRs from being submitted.
Thanks,
Daniel
On Thu, Mar 4, 2021 at 6:52 PM Shehzaad Nakhoda
wrote:
> Hi
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
chromedriver-binary
88.0.4324.96.0
13 matches
Mail list logo
