| commit | 8056dd129a2439e883d9df41cae113c0f0894643 | [log] [tgz] |
|---|---|---|
| author | Ruchir Rastogi <ruchirr@google.com> | Tue Mar 24 07:53:23 2020 -0700 |
| committer | Ruchir Rastogi <ruchirr@google.com> | Tue Mar 24 07:57:51 2020 -0700 |
| tree | 3c7eb10a557d1e2ae587a6b0726cfd97393ccc9e | |
| parent | baaf2a44fb48dd07a50e29eaadd596e9777bf6bd [diff] |
Support ERROR_ATOM_ID_INVALID_POSITION Originally, the native implementation would discard everything clients wrote to the buffer before the setAtomId call. Thus, the atom id was always placed in the "correct position." However, for consistency with the Java implementation, we now allow write calls before setAtomId to occur and log an error in that case. Test: bit libstatssocket_test:* Bug: 152119205 Change-Id: Ib109c7a939a5ae92c1d5fc70aa647ac7390fadad