Cautious Memory issueshttps://owo.codes/lambda/cautious-memory/-/issues2020-10-19T12:11:38Zhttps://owo.codes/lambda/cautious-memory/-/issues/22cm/recent reports "created" if a revision is the only recently2020-10-19T12:11:38Zlambda x162-lambda@users.noreply.owo.codescm/recent reports "created" if a revision is the only recently1) edit a page
2) wait a few weeks
3) edit it again
4) run cm/recent
## expected
bot reports that the page was edited
## actual
bot reports that the page was created1) edit a page
2) wait a few weeks
3) edit it again
4) run cm/recent
## expected
bot reports that the page was edited
## actual
bot reports that the page was createdhttps://owo.codes/lambda/cautious-memory/-/issues/18paginate cm/compare properly2020-02-11T06:52:59Zlambda x162-lambda@users.noreply.owo.codespaginate cm/compare properlycurrently the code block is split across pages. each page should be its own code block.currently the code block is split across pages. each page should be its own code block.https://owo.codes/lambda/cautious-memory/-/issues/17page edit listener connection gets dropped2019-12-22T10:34:29Zlambda x162-lambda@users.noreply.owo.codespage edit listener connection gets dropped> Pool is not suitable for long-running use-cases like a persistent event listener. Use an explicit connection wrapper instead. <br> […] an object that wraps a connection to set up the listener and re-connect automatically if the underly...> Pool is not suitable for long-running use-cases like a persistent event listener. Use an explicit connection wrapper instead. <br> […] an object that wraps a connection to set up the listener and re-connect automatically if the underlying connection is lost. Like the pool connection holder only without a pool.
https://github.com/MagicStack/asyncpg/issues/283#issuecomment-384657037