Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Correction:
So, the end result is that usb_write() sometimes sends a ZLP when it doesn't need to
should be
So, the end result is that usb_write() sometimes sends a ZLP when it doesn't need to, and sometimes neglects to send a ZLP when it should
So, the end result is that usb_write() sometimes sends a ZLP when it doesn't need to
should be
So, the end result is that usb_write() sometimes sends a ZLP when it doesn't need to, and sometimes neglects to send a ZLP when it should
da...@google.com <da...@google.com> #3
Note that the CHECK_LE has since been replaced with HandleError(), which causes adbd to not abort...but that stowaway amessage header is being dropped all the same...and so the behavior is pretty much undefined, I imagine. I'm not sure the switch to HandleError was a good idea, since it more or less swept the real problem under the rug.
Description
Version used: 2.1.0-alpha04
The stopTrackingTable function uses this look up to get to the table name (since 2.1.0):
final String tableName = mShadowTableLookup.get(tableId, mTableNames[tableId])
For FTS tables that lookup will return the name of the table that it is tracking, therefore dropping the triggers for the tracking table. When this happens no other observers / LiveData active on the table that the FTS table is tracking will receive any updates.