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

{
Issue 23841 spans several translation paths and provider-specific compatibility cases, requiring coordinated transformation fixes and broad regression coverage. Issue 32562 is narrower, primarily involving failure propagation and terminal-event handling within one streaming iterator flow, so it carries less implementation scope.
}
https://github.com/berriai/litellm/issues/23841 3:2 https://github.com/berriai/litellm/issues/32562

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

{
The right issue is harder because it involves asynchronous task-lifecycle behavior, third-party dependency compatibility, and startup/runtime regression risk. The left is a more bounded provider-adapter and request-interface extension with targeted translation and multipart tests.
}
https://github.com/berriai/litellm/issues/26700 5:3 https://github.com/berriai/litellm/issues/32456

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

{
#32201 is harder because it spans pass-through request/response handling, normalization, guardrail enforcement semantics, and likely streaming and regression-test coverage. #26700 is comparatively narrower: isolating an asynchronous lifecycle incompatibility and applying or coordinating a targeted SDK/workaround change.
}
https://github.com/berriai/litellm/issues/32201 3:1 https://github.com/berriai/litellm/issues/26700

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

{
The right issue is harder because it crosses streaming state management, exception propagation, protocol-compliant terminal signaling, and regression testing across multiple asynchronous failure paths. The left issue is more localized to request-shape translation and multipart image handling for one provider capability.
}
https://github.com/berriai/litellm/issues/32562 5:3 https://github.com/berriai/litellm/issues/32456

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

{
The left issue is harder because it requires coordinating asynchronous iterator failure handling, terminal-event guarantees, chained tool/LLM execution, and regression coverage across multiple streaming paths. The right issue is a broader input-translation enhancement, but it is comparatively bounded to multimodal normalization, MIME handling, and provider-specific tests.
}
https://github.com/berriai/litellm/issues/32562 3:2 https://github.com/berriai/litellm/issues/30501

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

{
The right issue is harder because it spans provider routing, authentication/endpoint compatibility, request-shape handling, and health-check behavior across shared proxy paths. The left issue is narrower: extending an existing provider-specific image-edit translation to carry one additional input, with focused multipart and regression-test changes.
}
https://github.com/berriai/litellm/issues/25394 5:3 https://github.com/berriai/litellm/issues/32456

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

{
The left issue entails designing and integrating a new extensibility contract across proxy routing, configuration, lifecycle, and compatibility boundaries. The right issue is a difficult distributed-state debugging and correctness fix, but its scope is more targeted once the failure path is isolated.
}
https://github.com/berriai/litellm/issues/25297 3:2 https://github.com/berriai/litellm/issues/30460

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

{
The left issue requires coordinated changes to asynchronous streaming state, exception propagation, terminal event semantics, and regression coverage across multiple failure paths. The right issue is comparatively localized to provider routing and health-check input handling.
}
https://github.com/berriai/litellm/issues/32562 4:1 https://github.com/berriai/litellm/issues/25394

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

{
#26535 is harder because it spans coordinated test infrastructure, provider coverage, CI integration, and release-compatible validation, whereas #32562 is a focused runtime error-propagation fix within one streaming subsystem.
}
https://github.com/berriai/litellm/issues/26535 5:2 https://github.com/berriai/litellm/issues/32562

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

{
26237 is harder because it requires coordinated changes across worker readiness, persistent-state recovery, refresh behavior, and request admission under partial infrastructure failure. 34328 is more localized to bounding and safely testing schema expansion across a small set of translation paths.
}
https://github.com/berriai/litellm/issues/26237 3:1 https://github.com/berriai/litellm/issues/34328