Upstream contributions
14
Merged upstream
8
Pull requests open
5
Repositories
4

Contribution log

llm-d/llm-d-router· #3931 ·

Keeping a request on one rollout revision across a conditional-decode miss in llm-d-router

Made the coordinator's conditional-decode step capture the response headers of a 412 cache miss, so the rollout revision header reaches the encode, prefill and decode phases. Merged as part 1 of #3931; the EPP half, which stamps the revision on the 412, needs a new opt-in plugin hook and is proposed separately.

  • Cross-component header contracts
  • Splitting a fix along ownership lines
  • Fail-closed vs silent fallback
Merged

Medium · LLM request routing / disaggregated serving coordinator

BerriAI/litellm· #49931 ·

Stop caching empty replies in LiteLLM's response cache

Replaced the response cache's 'has output' check with one that reads what each content block or chat message actually holds, so an empty reply is no longer cached or replayed on /v1/messages or /v1/chat/completions, streamed or not. A reply holding only Gemini's thought signature counts as empty, stored empty entries count as misses, and whitespace replies and code-completion fills stay cached. Checked with unit tests, an 8-mutant run, and two-worker proxies against real Gemini.

  • Cache admission policy
  • Streaming protocol parsing
  • Over-tightening guards
Merged

Medium · LLM gateway / response caching

BerriAI/litellm· #50024 ·

Keeping Azure reasoning intact on LiteLLM's /v1/messages route

Added a two-line Azure branch to _should_route_to_responses_api so a deployment that already resolves to Responses mode goes direct to the Responses adapter and replays encrypted reasoning. Plain Azure chat deployments stay on chat. Verified at the wire with respx; no live Azure run was possible, and that is stated in the PR.

  • Routing predicates
  • Scoping a fix to the failing path
  • Asserting on the wire body
Upstream Recognised

Medium · LLM gateway / provider routing

vllm-project/aibrix· #3372 ·

Why AIBrix clients got an error status with an empty body

Reproduced a flaky empty-error-body bug in the AIBrix gateway against Envoy 1.33.2 and traced it to Envoy's streamed ext_proc semantics: once headers are forwarded, a body-phase ImmediateResponse can only reset the stream. Showed the issue's suggested fix would still fail and proposed body_mutation on the final chunk instead. The issue author adopted that approach in the upstream fix PR.

  • Envoy ext_proc processing modes
  • Testing against the real proxy
  • Checking a suggested fix before building it
Upstream Recognised

Medium · AI gateway / Envoy ext_proc

llm-d/llm-d-router· #3680 ·

Warning about data producers nobody reads in llm-d-router

Added a startup warning in CreateMissingDataProducers for a configured producer key that no other plugin reads while a consumer of the same data type reads an auto-created default. It catches the issue's config and the cross-type prefix producers, and stays silent on every shipped config.

  • Dependency resolution
  • Plugin data graphs
  • False-positive budgets
Merged

Medium · LLM request routing / EPP data layer