You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unless I'm missing something, it seems the ACKQueue does not clean up after its self when you ACK the items. I discovered this function by looking over the unit tests. Is it expected that users call this function manually? It seems that clear_acked_data() should always be called after ackq.ack(item) if you don't want the sqlite DB to grow unbounded?
The text was updated successfully, but these errors were encountered:
I filed these as separate issues as I see this as a documentation issue. Basically, what this issue is asking is "do you expect users to explicitly call clear_acked_data()?" If so it should be added to the example in the readme and not left for someone to accidentally find it buried in the unit tests
Unless I'm missing something, it seems the ACKQueue does not clean up after its self when you ACK the items. I discovered this function by looking over the unit tests. Is it expected that users call this function manually? It seems that
clear_acked_data()
should always be called afterackq.ack(item)
if you don't want the sqlite DB to grow unbounded?The text was updated successfully, but these errors were encountered: