client_queues and messages tables grow unboundedly. QUEUE_MAX_AGE and MAX_HISTORY config options exist but are not enforced. Will eventually fill disk.
Suggested fix: Implement periodic pruning in the existing cleanup loop, using the already-defined config values.
## From QA Audit ([#25 comment](https://git.eeqj.de/sneak/chat/issues/25#issuecomment-10914))
**Severity: SHOULD-FIX**
`client_queues` and `messages` tables grow unboundedly. `QUEUE_MAX_AGE` and `MAX_HISTORY` config options exist but are not enforced. Will eventually fill disk.
**Suggested fix:** Implement periodic pruning in the existing cleanup loop, using the already-defined config values.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
From QA Audit (#25 comment)
Severity: SHOULD-FIX
client_queuesandmessagestables grow unboundedly.QUEUE_MAX_AGEandMAX_HISTORYconfig options exist but are not enforced. Will eventually fill disk.Suggested fix: Implement periodic pruning in the existing cleanup loop, using the already-defined config values.