Avi A

Hello, I've also encountered this issue while working with gitlab.com API. It seems that the "Retry-After", etc. headers are missing, hence the default wait_time set by `python-gitlab` is too low....

In addition to that change, I think it makes sense to log (in DEBUG level) that a rate limit 429 has occurred, but IDK how the maintainers would like to...

hey @nejch, thanks for looking at my PR. I guess I should've looked at open issues before opening it :) To your questions: 1. I ran into the rate limit...

@nejch I think it's going to take some time for gitlab.com to fix [the issue](https://gitlab.com/gitlab-org/gitlab/-/issues/365728). In the meantime I've been thinking and the exponential backoff will result in wait time...

(also, CI is failing because of the format of the commit message and IDK how to fix this besides submitting a new one)

Actually I'm witnessing a different issue when looking at `tracemalloc` output. In v1.9 I see that the pydantic module is building up its memory consumption. In lower version (v1.8.2) I...