The current char msg is not large enough for the error message.
Change to a std::string to avoid this problem completely.
Test: Ran atest FrameworksServicesTests on oriole_hwasan-userdebug
Test: verifying entire error message present.
Change-Id: I663bcbafd96572151395a9054b09764dc8e05b51
To improve security, the reason why an overlay transaction failed is
hidden from the caller unless OverlayManagerService.DEBUG is set to
true.
Tweak the logic to not hide the reason on userdebug and eng builds: this
will make it easier to debug tests that fail in CI while keeping the
code secure on user builds.
Test: manual: make executeAllRequests throw, test via `adb shell cmd overlay enable`, check error message
Change-Id: I1c35b9b24a01ea30a50398df9f250ad4e43c0686
Merged-In: I1c35b9b24a01ea30a50398df9f250ad4e43c0686
Currently the order of visible tasks we get is opposite to that in the
system.
This CL is to ensure that the visible focused task is on top, visible
tasks below, then invisible tasks. And keep the order within the
acquired focus, visible and invisible tasks groups consistent with
the system instead of sort by lastActiveTime.
If there are multiple DisplayContents, getTasks method will return:
[{VisibleFocusTask for DisplayTop, VisibleFocusTask for DisplayBottom},
{VisbleTask0...n1 for DisplayTop, VisbleTask0...n2 for DisplayBottom},
{InvisbleTask0...n3 for DisplayTop, InvisbleTask0...n4 for DisplayBottom}]
in the same result List.
Bug: 255255158
Signed-off-by: Bowen Li <libowen1@xiaomi.corp-partner.google.com>
Merged-In: I7f7d5e72fbf73988b58c23f8a11dff05dbc1b3f1
Change-Id: I7f7d5e72fbf73988b58c23f8a11dff05dbc1b3f1
* Previously, the height returned by Display#getSize was used to
determine visible objects. Based on the API level and the presence of
system decorations (e.g. notches), this can cause objects near the
bottom of the screen to be considered out of bounds (i.e. only objects
within y=0 and y=partial_height are considered even if the omitted
decorations are at the top of the screen).
Bug: 193270758
Bug: 188156320
Bug: 27537269
Test: manual
Change-Id: Iba21245c947cec0d0054f6d86e3585ba73233223
The fix is taken from AOSP patch aosp/2154236.
This will make sure the UI Automator always has the entire display to
interact with. Otherwise, in multi-windowing mode or on devices with
task bar, it will only be able to interact with the current focused
window, the default launch bounds, or the display excluding task bar,
depends on the actual scenario.
Test: PlatformSenarioTests
Bug: 238981445
Bug: 238985243
Bug: 238581838
Bug: 233945217
Change-Id: I9223ef5552ddb081e75de1242670862f2813e56d
(cherry picked from commit d1e350c7fc)
Merged-In: I9223ef5552ddb081e75de1242670862f2813e56d
This commit does:
- Skip the new retrying request when there is a pending retrying
task. Otherwise, the mRetryCount will be increased unexpectedly
before the current retrying task finishes its job.
- onChildOpened will call onSessionLost when MTU is invalid, and
onChildOpened will be called after onIkeOpened, so if
mRetryCount is reset in onIkeOpened, the mRetryCount will always
start from 0.
Bug: 256776571
Test: atest FrameworksNetTests:VpnTest
Manual test and check the log.
Change-Id: I396a3c279dc909f78c400cff1c31d77fe98cd7a6
This reverts commit ad0c6b5d8c.
Reason for revert: rolling forward the .so compression change. According to https://b.corp.google.com/issues/188859114#comment8, the underlying issue was fixed.
Bug: 254793035
Bug: 188859114
Fixes: 254793035
Fixes: 188859114
Change-Id: I4edc15d08527013206e3daf20c33ba29c87a01a2
Merged-In: I4edc15d08527013206e3daf20c33ba29c87a01a2
