diff options
| author | Christopher Tate <ctate@google.com> | 2016-04-27 18:16:17 -0700 |
|---|---|---|
| committer | Christopher Tate <ctate@google.com> | 2016-04-28 15:07:31 -0700 |
| commit | 98f1ff05580f85debaa245addd02777fe9e68273 (patch) | |
| tree | 6e7fdc1c8e53a46fc95a596e354e79e7368c8f74 /tools/aapt2/diff/Diff.cpp | |
| parent | a96986745f793407a4d83e2b94c620f9e7594c9d (diff) | |
Don't wedge full data backups by blocking the data consumer thread
In particular, don't ask the producer about error overrides when
it is still relying on the consumer to do its job first. This
needs to be policy for *any* transport-side error condition, not
just the one that was previously handled safely. Any transport-
initiated error "on the fly" means that the app-facing side of
the engine doesn't know to stop feeding data, and mustn't be
consulted with any blocking request.
We also now detect unexpected PACKAGE_REJECTED by the transport
after data streaming has begun, and translate that to the general
TRANSPORT_ERROR for correct handling down the line.
Bug 28399225
Bug 28375634
Change-Id: I613dc21bc9f2d23e6520eed6c3ac2e9dbc1d88dc
Diffstat (limited to 'tools/aapt2/diff/Diff.cpp')
0 files changed, 0 insertions, 0 deletions