Commit 2050d0b ("Traverse all hid/hidraw queued reports and return the
last one") aggressively started to clear all enqueued reports whenever a
read was done on a HID using hidapi.
While that seemed to work ok, it could cause important reports to be
lost, which might eventually break some drivers. As no contributor has
enough devices to test all drivers, it is better to be conservative and
only explicitly clear enqueued reports.
Notably, it is wiser to clear the queue before any writes that precede
one or more reads. This will clear stale data that has already been
queued, but will not risk loosing expected responses. And drivers that
expect reads to match specific writes should already be prepared to
handle what is left.
The objective is not definitively clear all previous reports, but simply
to avoid acting on (or forwarding to the user) stale data. The subtle
difference is that _stale_ presumes a delay of more than infinitesimal
length.
Related: #87 ("1.3.2 regression: kraken_two.get_status() returns wrong
fan RPM value")
fd4ccd70d0