You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@heron.apache.org by Ning Wang <wa...@gmail.com> on 2022/02/08 01:47:32 UTC

2/8/2022 Bi-Weekly OSS Heron Sync-up

Hello,

It has been two weeks since our last sync! Let's share our works for the
last two weeks in this thread. Thanks!


Regards,
--ning

Re: 2/8/2022 Bi-Weekly OSS Heron Sync-up

Posted by Nicholas Nezis <ni...@gmail.com>.
I've been a bit busy with my day job and life, but I'm slowly making
progress on testing updated Heron API jars which is one of the remaining
blockers for cutting a new release.

I also created the following 3 Issues in Github that I plan to resolve in
the near future. (Might not actually be me working on it, but I might have
team members contributing pull requests back for us to review.). These are
all related to Heron in Kubernetes.
https://github.com/apache/incubator-heron/issues/3769
https://github.com/apache/incubator-heron/issues/3770
https://github.com/apache/incubator-heron/issues/3771

On Mon, Feb 7, 2022 at 10:31 PM Saad Ur Rahman <sa...@apache.org>
wrote:

> Hello everyone,
>
> I have been researching and working on the migration of PEX build rules to
> native Bazel rules in the PR here:
> https://github.com/apache/incubator-heron/pull/3768
>
> I have learnt a lot about Bazel and a fair amount about building Protobuf
> within Bazel. The unfortunate reality is that there is only native support
> for C++, Java, and Golang Protobuf libraries. If we attempt to compile the
> Python Protobuf using custom genrules we will need to configure providers (
> https://docs.bazel.build/versions/main/skylark/rules.html#providers) for
> the native Bazel libraries rules to be able to assemble libraries. We would
> likely be removing the PEX rules and replacing them with custom Starlark
> rules. There is an excellent live article on the current state of Protobuf
> within the Bazel project here:
> https://aaliddell.github.io/SIG-rules-authors/proto-grpc
>
> My work to build the Heron Protobufs for Python, Java, and C++ is in the
> following repository under the "proto" directory.
> https://github.com/surahman/Heron-Protobuf
> https://github.com/surahman/Heron-Protobuf/tree/main/proto
> These Protobuf build rules were automatically generated by Gazelle after
> some configuration and will assemble the Protobuf libraries.
>
>
> On Mon, Feb 7, 2022 at 8:47 PM Ning Wang <wa...@gmail.com> wrote:
>
> > Hello,
> >
> > It has been two weeks since our last sync! Let's share our works for the
> > last two weeks in this thread. Thanks!
> >
> >
> > Regards,
> > --ning
> >
>

Re: 2/8/2022 Bi-Weekly OSS Heron Sync-up

Posted by Saad Ur Rahman <sa...@apache.org>.
Hello everyone,

I have been researching and working on the migration of PEX build rules to
native Bazel rules in the PR here:
https://github.com/apache/incubator-heron/pull/3768

I have learnt a lot about Bazel and a fair amount about building Protobuf
within Bazel. The unfortunate reality is that there is only native support
for C++, Java, and Golang Protobuf libraries. If we attempt to compile the
Python Protobuf using custom genrules we will need to configure providers (
https://docs.bazel.build/versions/main/skylark/rules.html#providers) for
the native Bazel libraries rules to be able to assemble libraries. We would
likely be removing the PEX rules and replacing them with custom Starlark
rules. There is an excellent live article on the current state of Protobuf
within the Bazel project here:
https://aaliddell.github.io/SIG-rules-authors/proto-grpc

My work to build the Heron Protobufs for Python, Java, and C++ is in the
following repository under the "proto" directory.
https://github.com/surahman/Heron-Protobuf
https://github.com/surahman/Heron-Protobuf/tree/main/proto
These Protobuf build rules were automatically generated by Gazelle after
some configuration and will assemble the Protobuf libraries.


On Mon, Feb 7, 2022 at 8:47 PM Ning Wang <wa...@gmail.com> wrote:

> Hello,
>
> It has been two weeks since our last sync! Let's share our works for the
> last two weeks in this thread. Thanks!
>
>
> Regards,
> --ning
>