Improving retry failure error message to differentiate between a 429 and 502 to prevent confusion for users. Recently had this come up where a gitlab endpoint was responding with a 502, yet GitBeaker was reporting failure due to 429 which was quite a rabbit hole 🐰 . Hopefully this will help prevent confusion for any users in the future.
Improving retry failure error message to differentiate between a 429 and 502 to prevent confusion for users. Recently had this come up where a gitlab endpoint was responding with a 502, yet GitBeaker was reporting failure due to 429 which was quite a rabbit hole 🐰 . Hopefully this will help prevent confusion for any users in the future.