Adding unsolicited events to response queue
results in doCommand() returning the wrong
result.
Pulling this change from master.
Bug: 3258529
Change-Id: I2a4b0bd8bb30b31682d7d61ee94a0d246bf10de2
If the sending of the command fails we should note it and not wait forever
for the response.
We should also not say we're ready until we actually are.
bug:2993205
Change-Id: I380f0312ac4693ad184a526b330fdfa23f6ac558
The buffer was being compacted in the read loop, but the start offset on
the compacted buffer wasn't being considered after the next read.
Bug: 2501075
Change-Id: I163297d751cf800d0bbc66df66b1a0fa0785de49
In NativeDaemonConnector.doCommand() calls, there was inconsistent error
checking. This change adds error checking for every call and makes it so
that any call to .doCommand() that gets an error code won't cause the
code to hang forever.
Change-Id: I4584953a759a48ad16adfe8ee9e564b5f5796680
If NativeDaemonConnector hits its buffer limit, it would truncate the
data and lose some information. This change compacts the buffer and then
retries to read the rest of the data.
Change-Id: I0d5fee097bdd6808212ef3ad6fb4abbc6310fd4a
This class provides an interface to communicate with native daemons using the
libsysutils framework communication code.
Signed-off-by: San Mehat <san@google.com>
NativeDaemonConnector: fix whitespace
Signed-off-by: San Mehat <san@google.com>
NativeDaemonConnector: Fix review comments
Signed-off-by: San Mehat <san@google.com>
NativeDaemonConnector: On an error, re-try the connection
Signed-off-by: San Mehat <san@google.com>
