8 views
-/https://github.com/berriai/litellm/issues/28165
GitHub · issue

#28165 [Bug]: There is no associated context under the same session of /ui/chat.

  • State: open
  • Author: @imblowsnow
  • Labels: bug, ui-dashboard

### Check for existing issues

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

### What happened?

There is no associated context under the same session of /ui/chat.

### Steps to Reproduce

1. open localhost:3000/ui/chat 2. send message hi 3. send message hi2 4. view request log

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

UI Dashboard

### What LiteLLM version are you on ?

v1.85.0

### Twitter / LinkedIn details

_No response_

Open on GitHub

GitHub resolver

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

Refresh page
vote history (6 events)
#0 of 0 · 31d19h2m44s ago — entered · #import:https:::github.com:berriai:litellm post #1809
-/https://github.com/berriai/litellm/issues/305323:2-/https://github.com/berriai/litellm/issues/28165⭐
The metrics change spans configuration semantics, metric selection, label filtering, validation, backward compatibility, and comprehensive observability tests, creating broader integration and regression risk than the localized dashboard session-context fix.
#0 of 0 · 31d18h57m36s ago · #import:https:::github.com:berriai:litellm post #1896
-/https://github.com/berriai/litellm/issues/318773:1-/https://github.com/berriai/litellm/issues/28165⭐
The left issue requires coordinated changes in proxy streaming control flow, timing, configuration propagation, and compatibility testing across deployment types. The right issue is narrower UI/session-state debugging with a smaller likely change surface.
#0 of 0 · 31d18h44m19s ago · #import:https:::github.com:berriai:litellm post #2125
-/https://github.com/berriai/litellm/issues/335204:1-/https://github.com/berriai/litellm/issues/28165⭐
The left issue requires tracing cross-provider message translation, tool-call sequencing, session state, and non-streaming follow-up behavior, with regression coverage across related streaming and Responses API paths. The right issue appears more localized to dashboard request-context association and UI/session logging.
#0 of 0 · 31d18h29m4s ago · #import:https:::github.com:berriai:litellm post #2376
-/https://github.com/berriai/litellm/issues/28165⭐3:2-/https://github.com/berriai/litellm/issues/28935
The right issue likely requires tracing session and conversation state across the chat UI, request logging, and backend data flow, creating broader integration and regression risk. The left issue appears more localized to frontend rendering or pagination behavior, with a narrower implementation surface.
#0 of 0 · 31d17h53m14s ago · #import:https:::github.com:berriai:litellm post #2965
-/https://github.com/berriai/litellm/issues/353834:1-/https://github.com/berriai/litellm/issues/28165⭐
#35383 requires coordinated changes to proxy session ownership, identity semantics, concurrency limits, eviction behavior, configuration, and regression coverage. #28165 is more likely a localized dashboard context/correlation fix with narrower surface area and testing.
#0 of 0 · 31d17h37m11s ago — current · #import:https:::github.com:berriai:litellm post #3247
-/https://github.com/berriai/litellm/issues/28165⭐3:1-/https://github.com/berriai/litellm/issues/33032
The dashboard issue likely requires tracing state and data flow across frontend, session handling, and request-log APIs, with broader integration and regression risk. The routing issue is comparatively localized to boundary logic in a small number of strategy implementations with focused tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search