Robert Raposa

Other thoughts to consider: How might different solutions affect traceability and rate limiting. Note: If we enhance the client with additional features around retries, backoffs, circuit breakers, etc., we'll have...

Note that once this ADR exists, there should be a follow-up ticket for getting the platform aligned with the decision.

Additional notes: * Review the original client for code that was lost. For example, the setting of the `User-Agent` here: https://github.com/openedx/edx-rest-api-client/blob/2388c71aa0c782720f40491ad75a4bce6bf68dbf/edx_rest_api_client/client.py#L355C25-L355C37 * Updated code did not use a new client,...

If we are unable to make a decision, we could at a minimum document the de facto decision that was made for all the legacy code in a how-to and/or...

Note that in general we should be avoided doing synchronous calls to other services within a user's request. This is one reason why we may want to avoid reuse of...

I'd really like this to get someone's attention, because the failing uploads that breaks PRs is a frustration that many people are probably feeling. I guess we have scripts where...

@kdmccormick: I see. I didn't realize this issue was in edx-cookiecutters, and I was really asking about existing repos, like openedx-events where I saw a recent codecov upload failure. >...

Note that the ticket https://github.com/edx/edx-arch-experiments/issues/528 to implement an alternative got blocked/abandoned due to 2U organization issues.

Apologies that I missed your ping. My team no longer maintains this repo. The repo should designate the maintainer if there is one. I’ll ask.

Thanks @CodeWithEmad. Those seem like reasonable arguments to me, but we'll see how @feanil feels. Note that code blocks that include both a command and example output would be a...