Welcome Guangming

On Mon, Oct 10, 2022 at 10:33 AM Hu go <uestc.h...@gmail.com> wrote:

> Welcome~
>
> On Mon, Oct 10, 2022 at 10:27 AM Wang,Weibing <wwb...@gmail.com> wrote:
>
> > Welcome!
> >
> > On Mon, Oct 10, 2022 at 10:24 AM 陈光明 <chenguangmin...@foxmail.com>
> wrote:
> > >
> > > Hey guys,
> > >
> > > I'm Guangming Chen, from the yy company, mainly responsible for
> > developing and maintaining C++ microservice based on bRPC framework.
> > >
> > > My GitHUb address is https://github.com/chenBright . Here are my
> > contributions:
> > >
> > >
> > > Fix the problem that the channel initialization failed due to the long
> > list of ip resolved by DNS.
> > >
> > >
> > >
> > > Fix the problem that the additional refrerence can not release when
> > socket is reviving.
> > >
> > >
> > >
> > > Fix ssl state exception coredump problem.
> > >
> > >
> > >
> > > Fix the problem that AfterHCCompleted is not be called when
> WaitAndReset
> > fails.
> > >
> > >
> > >
> > > Fix the problem that the first bthread keytable on worker pthread will
> > be deleted twice.
> > >
> > >
> > >
> > > chore: update company case
> > >
> > >
> > >
> > > Add an option to use baidu-std error code in http response.
> > >
> > >
> > >
> > > Fix typo in json2pb doc.
> > >
> > >
> > > More details can be found here at:
> >
> https://github.com/apache/incubator-brpc/pulls?q=is%3Apr+author%3AchenBright+
> > >
> > > In my job, I learn a lot from bRPC framework , a high-performance,
> > stable, easy-to-use, well-designed and well-documented RPC framework.
> > Thanks Weibing Wang for the invitation. I am honoured to have been
> invited
> > to become a committer. Whether successful or not, I will contribute more
> to
> > the community and make bRPC a better RPC framework.
> > >
> > >
> > >
> > >
> > > Thanks and best regards,
> > >
> > > Guangming Chen
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
> > For additional commands, e-mail: dev-h...@brpc.apache.org
> >
> >
>

Reply via email to