[GitHub] [incubator-brpc] zyearn commented on issue #1047: brpc 是否没法保证一个连接上的请求顺序处理?有参数可以控制吗?

2020-02-25 Thread GitBox
zyearn commented on issue #1047: brpc 是否没法保证一个连接上的请求顺序处理?有参数可以控制吗?
URL: https://github.com/apache/incubator-brpc/issues/1047#issuecomment-591287893
 
 
   redis场景和你的场景是一样的,可以参考下brpc redis的实现。


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org



[GitHub] [incubator-brpc] yichenluan commented on issue #1047: brpc 是否没法保证一个连接上的请求顺序处理?有参数可以控制吗?

2020-02-25 Thread GitBox
yichenluan commented on issue #1047: brpc 是否没法保证一个连接上的请求顺序处理?有参数可以控制吗?
URL: https://github.com/apache/incubator-brpc/issues/1047#issuecomment-591266256
 
 
   补充说明:我在实现 Server 端,且是自定义协议。


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org



[GitHub] [incubator-brpc] yichenluan opened a new issue #1047: brpc 是否没法保证一个连接上的请求顺序处理?有参数可以控制吗?

2020-02-25 Thread GitBox
yichenluan opened a new issue #1047: brpc 是否没法保证一个连接上的请求顺序处理?有参数可以控制吗?
URL: https://github.com/apache/incubator-brpc/issues/1047
 
 
   如题,我的场景客户端会发送一批 in-flight 的请求,同时要求服务端对这些请求顺序处理并返回。
   
   请问在 brpc 下该如何做到呢?
   
   我认为理想的情况是我可以在收到一个完整 request 后 mute 掉该 socket 的读,当我回完 response 后再解 
mute,当然要是有参数能直接控制就更好了。
   
   @jamesge 


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org



Re: [VOTE] Release Apache brpc(incubating) 0.9.7-rc03

2020-02-25 Thread tan zhongyi
Hi, JB and kevin,
Please help, 
thanks a lot.



在 2020/2/24 上午11:37,“tan zhongyi” 写入:


Hi, kevin & JB,

The vote for release on incubator mail list is still ongoing.
We got 2 +1(binding) from Justin and Von.
And We need your help to vote.

Please help, thanks


在 2020/2/21 下午10:56,“vongosling” 写入:

Hi,

+1 (binding)

I checked:
- signatures and hashes fine
- LICENSE and NOTICE is basically ok(there is still a category b 
dependency
in the source code)
- All necessary files have license headers

To Willem Jiang, the problem I listed last time was the main license
issue(category X should be removed and may keep the category b 
dependency
in binary ) :-)

Best Regards,
Von Gosling

tan zhongyi  于2020年2月21日周五 下午5:21写道:

> Yes, we will fix these issues later,
> so we add WIP disclaimer as Justin suggested.
> Thanks
>
>
>
> 在 2020/2/19 下午7:36,“Justin Mclean” 写入:
>
> Hi,
>
> > From my understanding, for the CDDL license and LGPL license
> > dependencies, if we don't modify the code, it should be fine.
>
> You can’t have a category X dependancy unless it’s optional. So 
GPL or
> LGPL dependancies are in general not allowed. See [1]
>
> Thanks,
> Justin
>
> 1. https://www.apache.org/licenses/GPL-compatibility.html
> 
-
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
>

-- 
Nothing is impossible


-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org



Podling Brpc Report Reminder - March 2020

2020-02-25 Thread jmclean
Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 18 March 2020, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, March 04).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/March2020

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org



[GitHub] [incubator-brpc] niukuo commented on issue #859: 链接jemalloc后可能会有死锁的问题

2020-02-25 Thread GitBox
niukuo commented on issue #859: 链接jemalloc后可能会有死锁的问题
URL: https://github.com/apache/incubator-brpc/issues/859#issuecomment-590851992
 
 
   临时解决方式: 设置 bvar_collector_expected_per_second=0


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org



[GitHub] [incubator-brpc] niukuo commented on issue #859: 链接jemalloc后可能会有死锁的问题

2020-02-25 Thread GitBox
niukuo commented on issue #859: 链接jemalloc后可能会有死锁的问题
URL: https://github.com/apache/incubator-brpc/issues/859#issuecomment-590849867
 
 
   bthread::submit_contention 
中butil::get_object()在线程第一次调用时会初始化tls,分配内存。


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@brpc.apache.org
For additional commands, e-mail: dev-h...@brpc.apache.org