[WIP]: add async support to tls_fetcher/proxy and qos #524
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 task
Turnalek
force-pushed
the
ales/async_proxy
branch
4 times, most recently
from
85d5895 to
3667ab4
Compare
Turnalek
commented
May 15, 2025
Turnalek
force-pushed
the
ales/async_proxy
branch
10 times, most recently
from
7aeca11 to
65672b2
Compare
Turnalek
force-pushed
the
ales/async_proxy
branch
6 times, most recently
from
6810191 to
f4d01f0
Compare
Turnalek
force-pushed
the
ales/async_proxy
branch
5 times, most recently
from
f372272 to
b55c07f
Compare
Turnalek
force-pushed
the
ales/async_proxy
branch
3 times, most recently
from
63dea23 to
0a38b9b
Compare
fixes a loop problem with async also adds integration test to test out qos_host and qos_core (aka Reaper)
Turnalek
force-pushed
the
ales/async_proxy
branch
from
0a38b9b to
87cb159
Compare
allows easier local testing
Turnalek
force-pushed
the
ales/async_proxy
branch
from
189d6e5 to
1949ced
Compare
to test the parallelism with tls-fetcher
Turnalek
force-pushed
the
ales/async_proxy
branch
18 times, most recently
from
7f36b05 to
24b0140
Compare
Turnalek
force-pushed
the
ales/async_proxy
branch
from
03ee617 to
2857b00
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary & Motivation (Problem vs. Solution)
Implement async qos_net::AsyncProxy
this includes:
-
Reaper::execute_async [qos_core]-
AsyncStream [qos_core]-
AsyncPool/AsyncStream [qos_core]-
AsyncListener [qos_core]-
AsyncRequestProcessor [qos_core]-
AsyncProxyConnection [qos_net]-
AsyncProxy [qos_net]-
AsyncProxyStream [qos_net]-
AsyncHostServer [qos_host]as well as fixing qos_next's qos_core "vm" feature dependency issue by only requiring it if qos_net is requested with it, adding new integration tests and fixing
qos_test_primitivesshutdown handling on unix (SIGINT)New dependencies:
[email protected][email protected][email protected]-> was added in some places but we already used it beforeNOTE: still marked WIP as we need to test in preprod, but the code should be generally review-worthy. There will have to be one more change in
initbut we still need to decide how to approach that after we confirm everything works.How I Tested These Changes
Locally only so far
Pre merge check list