Fix unhandled exception raised at runtime: 'x-ratelimit-remaining'

[den-is]

Fixing #57

P.S.: My default black config formatted code a little bit.

[JonasKs]

Hi 😊 Thanks for the PR.

P.S.: My default black config formatted code a little bit.

It's already implemented black in this project (see the failing linting pipeline), but our config differs from yours. It's used through pre-commit. Simply write pre-commit install in your repo, and then pre-commit run --all-files and it'll be fixed. (Require you to install pre-commit first)

[sondrelg]

This looks good to me. Just curious @den-is, have you had a chance to test this version of the code on your own projects? I've migrated my images to ECR, so no longer have a real project to try things like this on hehe 🤷

[den-is]

This looks good to me. Just curious @den-is, have you had a chance to test this version of the code on your own projects? I've migrated my images to ECR, so no longer have a real project to try things like this on hehe 🤷

Yes, it was/is successfully working for months on a scheduled basis.
But action/execution still was hitting GH rate-limits, Looks like this async code requires some "semaphores". While it was hitting GH rate-limits it still was doing its job and was cleaning the registry.

I'm not working on that project and don't have access to such GHCR anymore.

[sondrelg]

OK sounds good. I'll try and get this released now! 👍