-
Notifications
You must be signed in to change notification settings - Fork 344
Conversation
Hm, looks like release build is hanging. I'll investigate locally. |
Trying out an idea to fix the build hanging. If it works, I'll clean up then ping for review. |
r? @davidfowl Build is green, but I'm not totally confident about it. I think it needs a few more runs. |
@KodrAus, any updates to this PR? |
@ahsonkhan I can't reproduce the flakiness locally so have put a I still think it's worth a review because the code before simply didn't work. So assuming the rest is good I guess we can either:
I'm happy with whatever approach. |
I will let @davidfowl. @pakrym comment on that. |
for (int loop = 0; loop < ClientCount; loop++) | ||
{ | ||
using (var thread = new UvThread()) | ||
using (var connection = await new UvTcpClient(thread, endpoint).ConnectAsync()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use a sockets client
@davidfowl Switched to socket client, which surfaced the many problems with my test. I've fixed those up. I've made the RIO server a lot slower, but at least we know it works now. |
@davidfowl, comments? |
@davidfowl any more feedback? |
Does it work now? @benaadams did you take a look? |
Yep, it totally works now. |
ping @benaadams @davidfowl, @KodrAus, is this good to go? |
@ahsonkhan It's just waiting on a review |
@davidfowl, @benaadams - please take a look |
@KodrAus, is this change still relevant? If so, can you please fix the merge conflict? Ty. @davidfowl, @benaadams, @KrzysztofCwalina - are we taking this PR? If not, we should close it. |
@ahsonkhan I haven't looked at this in a while. I'll take a look at the conflict, this might not be needed anymore. |
Closing this PR. Please feel free to re-open if necessary. |
Rebase of #1420
Fixes an issue with
RioTcpConnection
s not flushing receives.cc: @davidfowl @benaadams
Changes:
RioThread
is in a valid state before from ctorRioTcpServer