Sorting LiteLLM GitHub issues by difficulty to implement. Higher = harder.

{
#35528 is harder because it changes failure semantics across asynchronous rate-limiting, Redis/cache integrations, exception classification, and enforcement tests, with significant risk of either bypassing limits or breaking intentional no-configuration and HTTP error paths. #31873 is comparatively contained to context propagation and JSON formatting, with limited call-site impact and straightforward opt-in tests.
}
https://github.com/berriai/litellm/issues/35528 3:1 https://github.com/berriai/litellm/issues/31873