6 views
-/https://github.com/berriai/litellm/issues/30762
GitHub · issue

#30762 [Bug/Docs]: Snowflake (snowflake/) provider: streaming tool-calls dropped, misleading endpoint docs, and gaps using the OpenAI-/Anthropic-compatible Cortex endpoints

  • State: open
  • Author: @BHOGISAISATHWIK
  • Labels: bug, llm translation, SDK

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

### Summary

Using litellm (SDK / Router) with Snowflake Cortex, I hit a cluster of related issues — some in the `snowflake/` provider code, some in the docs, and some when following the docs' suggestion to use the OpenAI-/Anthropic-compatible Cortex endpoints. Filing together for context; happy to split. Verification status tagged per item (source-checked on `main` 2026-06-18 unless noted).

Background: Snowflake Cortex exposes three REST endpoints — `/api/v2/cortex/inference:complete` (native), `/api/v2/cortex/v1/chat/completions` (OpenAI-compatible), `/api/v2/cortex/v1/messages` (Anthropic-compatible). The litellm `snowflake/` provider only ever targets `inference:complete`.

---

### Issue 1 — `snowflake/` drops `tool_calls` when streaming [BUG, verified on main]

`SnowflakeConfig.transform_response` converts Cortex `content_list`/`tool_use` → OpenAI `tool_calls`, but **only for non-streaming**. There is no `get_model_response_iterator` / `chunk_parser`, so streaming inherits the generic `OpenAIGPTConfig` SSE pa…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (5 events)
#0 of 0 · 31d19h1m20s ago — entered · #import:https:::github.com:berriai:litellm post #2054
Model omitted braces; inferred difficulty from issue scope and surface area.
The right issue spans provider behavior, streaming, endpoint compatibility, and documentation across multiple integration paths, creating broader testing and regression risk. The left issue is a focused but cross-cutting pricing-model change with time-aware calculation and backward-compatibility concerns.
The right-hand issue spans provider behavior, streaming translation, endpoint compatibility, and documentation, requiring coordinated implementation and broader regression coverage. The left-hand issue is a localized parser hardening change with relatively contained testing.
The right-hand issue spans multiple integration layers, including provider behavior, streaming translation, endpoint compatibility, and documentation, creating substantially broader testing and regression risk. The left-hand issue appears more localized to proxy authentication configuration and request-path handling.
#0 of 0 · 31d18h23m25s ago — current · #import:https:::github.com:berriai:litellm post #2665
The right issue has broader cross-layer scope, involving provider behavior, streaming adaptation, endpoint compatibility, documentation, and integration coverage. The left is a comparatively contained metadata fallback and presentation fix.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search