Nutomic
The cursor needs to point to a specific row on that table, if you only have `person_id` it would return many different rows. By the way it would make sense...
The default rate limit for read actions is 180 requests per 60s. This means if you sleep for 333ms after each request, you will never get any rate limit error.
It seems Piefed solved this by adding a separate API endpoint: https://codeberg.org/rimu/pyfedi/issues/884#issuecomment-5994619
To be honest I dont really understand how all this works. @christianjuth Did you test to confirm that Piefed solves this problem on posts with hundreds of comments?
I assume this doesnt require any breaking change, removing it from 1.0 milestone then.
Now is definitely the perfect time to make breaking changes. And database optimization is something we can use a lot of help with, so thanks for looking into this! >...
#5556 adds a few more joins to post_view and comment_view to detect bans from different instances. This brings up the number of joins from 9 to 11 for each of...
I fixed that one already. Now theres another error: `failed to build: tag is needed when pushing to registry`. But the tag param is unchanged from before...
Same error after restart Edit: Here are the docs btw: https://codeberg.org/woodpecker-plugins/docker-buildx/src/branch/main/docs.md#multi-registry-push-example
> https://codeberg.org/woodpecker-plugins/docker-buildx/issues/156 mentions tagging issue might be related to newlines not generating properly? This is about tags_file which we dont use. > try using tag: dev or tags: dev and...