vllm-project / vllm-project/aibrix

[Bug] Deployment detail page uses hardcoded data and cannot open the real Playground

Open
#2,495 1 comment 0 reactions 0 assignees View on GitHub
area/website help wanted kind/bug priority/important-soon
Dominant language
Go
Stars
5.1k
Forks
694
Avg merge
1d 19h
Merged PRs (30d)
98

Description

The deployment detail page fetches a real Deployment record, but much of the page is still sample UI:

- the inference URL and model ID are [hardcoded](https://github.com/vllm-project/aibrix/blob/a40be9ba404730e4be2d2a0820942bca79275dc6/apps/console/web/src/components/DeploymentDetail.tsx#L56-L63);
- account names, description, timestamp, and resource names are [static values](https://github.com/vllm-project/aibrix/blob/a40be9ba404730e4be2d2a0820942bca79275dc6/apps/console/web/src/components/DeploymentDetail.tsx#L69-L98);
- Copy, View More, and Open in Playground do not perform their advertised actions.

The Playground is also not connected yet. It [lists catalog models](https://github.com/vllm-project/aibrix/blob/a40be9ba404730e4be2d2a0820942bca79275dc6/apps/console/web/src/components/Playground.tsx#L475-L498) and [streams a fixed local response](https://github.com/vllm-project/aibrix/blob/a40be9ba404730e4be2d2a0820942bca79275dc6/apps/console/web/src/components/Playground.tsx#L546-L597). A real backend proxy already exists at `POST /api/v1/playground/chat/completions` ([handler](https://github.com/vllm-project/aibrix/blob/a40be9ba404730e4be2d2a0820942bca79275dc6/apps/console/api/handler/playground.go#L63-L138)).

The detail page should use real Deployment/Model data and show a usable endpoint and serving model name. The current [Deployment API](https://github.com/vllm-project/aibrix/blob/a40be9ba404730e4be2d2a0820942bca79275dc6/apps/console/api/proto/console/v1/console.proto#L55-L70) may need a few additional fields, including creation time and inference metadata.

Open in Playground should carry the selected deployment (or serving name) to `/playground`. The Playground should list callable deployments and send the actual request through the existing proxy instead of using the local timer. Please also wire up the displayed copy actions and avoid showing unsupported code examples as functional.

A local test with the mocked app should cover: create deployment → open detail page → open Playground → receive a real chat completion.

Depends on #2494 for Gateway discovery. Related: #2202, #2198.

Contributor guide

Open the contributing guide

Research direction

Start in apps/console/web/src/components/DeploymentDetail.tsx and Playground.tsx, then read the Deployment API definition in apps/console/api/proto/console/v1/console.proto and the existing proxy in apps/console/api/handler/playground.go. Trace the mocked app flow from deployment creation through navigation and chat completion. Done means real deployment data and actions are shown, Open in Playground selects the deployment, and the mocked end-to-end flow receives a real completion through the proxy.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, typescript
Domain
api, full-stack, testing
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.