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

{
The right-hand issue is harder because it requires coordinating failure-safe state ownership, retry behavior, concurrency, and recovery across multiple production paths, with broader regression testing. The left-hand issue is comparatively localized to cache update and eviction semantics with a narrower behavioral fix.
}
https://github.com/berriai/litellm/issues/33873 4:1 https://github.com/berriai/litellm/issues/34681