[FIX] Upgrade litellm to 1.82.3 to fix Azure OpenAI connection errors#1870
[FIX] Upgrade litellm to 1.82.3 to fix Azure OpenAI connection errors#1870hari-kuriakose merged 2 commits intomainfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (10)
📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
Summary by CodeRabbit
WalkthroughThe Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@unstract/sdk1/pyproject.toml`:
- Line 30: The pyproject.toml bump to "litellm==1.82.3" in unstract/sdk1 is
inconsistent with other modules pinned to 1.81.7 (unstract/workflow-execution
and unstract/connectors); either align versions or document/guard the
divergence. Fix by updating the litellm dependency in the other modules'
pyproject.toml files to 1.82.3 (or revert sdk1 to 1.81.7) so all
runtime-interacting packages use the same version, or add an explicit comment
and release note in each module (unstract/sdk1, unstract/workflow-execution,
unstract/connectors) explaining why mixed versions are safe and add integration
tests to exercise cross-module flows with the two versions.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 6b89cef8-e776-4175-a285-1468fd093855
⛔ Files ignored due to path filters (8)
backend/uv.lockis excluded by!**/*.lockplatform-service/uv.lockis excluded by!**/*.lockprompt-service/uv.lockis excluded by!**/*.lockunstract/filesystem/uv.lockis excluded by!**/*.lockunstract/sdk1/uv.lockis excluded by!**/*.lockunstract/tool-registry/uv.lockis excluded by!**/*.lockuv.lockis excluded by!**/*.lockworkers/uv.lockis excluded by!**/*.lock
📒 Files selected for processing (1)
unstract/sdk1/pyproject.toml
Greptile SummaryThis PR upgrades Key changes:
Confidence Score: 5/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant PS as prompt-service
participant SDK as unstract-sdk1
participant LL as litellm 1.82.3
participant Cache as LLMClientCache
participant AZ as AzureOpenAI SDK
participant HTTP as httpx Transport
PS->>SDK: LLM completion request
SDK->>LL: completion()
LL->>Cache: get_or_create client
Cache->>AZ: AzureOpenAI(httpx_client=...)
AZ->>HTTP: attach transport
Note over Cache,HTTP: 1.81.7 bug: TTL/size eviction closed httpx transport
Note over Cache,HTTP: 1.82.3 fix: client cleanup deferred to shutdown only
LL->>AZ: chat.completions.create()
AZ->>HTTP: send request
HTTP-->>AZ: response (no RuntimeError)
AZ-->>LL: completion result
LL-->>SDK: LLMResponse
SDK-->>PS: success
Reviews (3): Last reviewed commit: "Updated other lockfiles to reflect litel..." | Re-trigger Greptile |
6eb29f3 to
342428d
Compare
|
hari-kuriakose
left a comment
There was a problem hiding this comment.
@pk-zipstack LGTM overall
Test ResultsSummary
Runner Tests - Full Report
SDK1 Tests - Full Report
|



What
1.81.7to1.82.3inunstract/sdk1/pyproject.tomlWhy
LLMClientCachewhere cached httpx clients are closed on cache eviction (TTL expiry or max-size overflow), but still-cachedAzureOpenAISDK clients hold references to the now-closed httpx transportRuntimeError: Cannot send a request, as the client has been closed, surfacing aslitellm.APIConnectionError: AzureException APIConnectionError – Connection errorin prompt-serviceHow
1.81.7to1.82.3Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
== 1.81.7) will need a separate update in its own branch.Database Migrations
Env Config
Relevant Docs
Related Issues or PRs
Dependencies Versions
litellm:1.81.7→1.82.3Notes on Testing
APIConnectionErrorregression after deploymentScreenshots
N/A
Checklist
I have read and understood the Contribution Guidelines.