-
Notifications
You must be signed in to change notification settings - Fork 908
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[C] async DNS res for the C media driver #1566
Conversation
…ts to the async thread
aeron-client/src/main/c/concurrent/aeron_blocking_linked_queue.c
Outdated
Show resolved
Hide resolved
aeron-client/src/main/c/concurrent/aeron_blocking_linked_queue.c
Outdated
Show resolved
Hide resolved
aeron-client/src/main/c/concurrent/aeron_blocking_linked_queue.c
Outdated
Show resolved
Hide resolved
aeron-client/src/main/c/concurrent/aeron_blocking_linked_queue.c
Outdated
Show resolved
Hide resolved
aeron-client/src/main/c/concurrent/aeron_blocking_linked_queue.c
Outdated
Show resolved
Hide resolved
aeron-client/src/main/c/concurrent/aeron_spsc_concurrent_linked_queue.c
Outdated
Show resolved
Hide resolved
aeron-client/src/main/c/concurrent/aeron_spsc_concurrent_linked_queue.c
Outdated
Show resolved
Hide resolved
aeron-client/src/main/c/concurrent/aeron_spsc_concurrent_linked_queue.c
Outdated
Show resolved
Hide resolved
aeron-client/src/main/c/concurrent/aeron_spsc_concurrent_linked_queue.c
Outdated
Show resolved
Hide resolved
aeron-client/src/main/c/concurrent/aeron_spsc_concurrent_linked_queue.h
Outdated
Show resolved
Hide resolved
aeron-client/src/main/c/concurrent/aeron_spsc_concurrent_linked_queue.c
Outdated
Show resolved
Hide resolved
…uctor_on_add_network_publication, error handling is a work in progress
…ment condition variables
…ver conductor tests
…t an async event in flight
@nbradac You need to pull from master again. |
} | ||
else | ||
{ | ||
// TODO set current errcode/errmsg to what was handed to this function??? |
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.
I think we do have to set those if we are going to use them below as they are thread local variables. Can we put together a system test that will trigger this code path to see what would happen?
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.
Right now, the only time the async_client_command->on_error
is used we don't check to see what the error was. The original code just set ss_family = AF_UNSPEC
and proceeded as normal. The new code sets the on_error callback so that we have an opportunity to set AF_UNSPEC, but it then just calls the _complete() callback directly. So I'm not sure we've got a good way to test this out at the moment - i.e. even if I set the errcode and errmsg thread local variables here, nobody ever reads them, so it won't matter.
No description provided.