fix(windows-agent): Delegates agent.WaitReady
to the daemon
#982
+71
−5
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.
Since #896 the agent might sometimes close the
a.ready
channel too early, giving the possibility of a call toa.WaitReady()
exiting before the daemon really starts serving, thus not really waiting.The deamon knows best when is the most likely moment to be serving, thus this PR slightly modifies
a.WaitReady()
to check with the daemon, which had to implement its owndaemon.WaitReady()
.The
a.ready
channel is still useful to synchronize the access toa.daemon
, preventing nil pointer access when the deamon is not yet initialized. Checking fornil
is still needed, as thea.ready
channel may be closed without ever serving, such as on a failure case.This adds a test for
daemon.WaitReady()
, but the agent tests don't need to change, as their "flakyness" reveal the problem.UDENG-4900