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

{
Issue #32221 is harder because it spans multiple synchronous and asynchronous retry paths and must preserve correct exception propagation, HTTP status handling, spend logging, callbacks, and router fallback behavior. Issue #31838 is comparatively localized to adding Redis cache invalidation across customer mutation endpoints and covering it with targeted tests.
}
https://github.com/berriai/litellm/issues/32221 4:1 https://github.com/berriai/litellm/issues/31838